You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the analytics web page, when we specify "Day: Detail" we would expect to see the daily details for only the services we selected.
A typical use case would be as follows. I select only "attacks", then want to see the details the IP addresses used, HTTP method, etc. We can therefore correlate information and identify if they are real attacks or bugs in some of our apps. By checking the daily details of attacks we could quickly identify the recurrent attackers/buggers.
Such details per service are available in the summary.txt file produced by the log miner.
When selecting multiple services, we should probably list the details for each of them separately. Trying to aggregate them is probably difficult, yet impossible, since we have things like the buckets for "X others", where sometimes an item can be in the "X others" for one service but not to the other and there is no way (?) to identify.
The text was updated successfully, but these errors were encountered:
In the analytics web page, when we specify "Day: Detail" we would expect to see the daily details for only the services we selected.
A typical use case would be as follows. I select only "attacks", then want to see the details the IP addresses used, HTTP method, etc. We can therefore correlate information and identify if they are real attacks or bugs in some of our apps. By checking the daily details of attacks we could quickly identify the recurrent attackers/buggers.
Such details per service are available in the summary.txt file produced by the log miner.
When selecting multiple services, we should probably list the details for each of them separately. Trying to aggregate them is probably difficult, yet impossible, since we have things like the buckets for "X others", where sometimes an item can be in the "X others" for one service but not to the other and there is no way (?) to identify.
The text was updated successfully, but these errors were encountered: