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
I noticed that there are many more visitors on my website since v1.7.0. This seems cool, but I was a little bit pessimistic and thus looked into the server logs.
I noticed that the Icinga uptime check is no more recognised as bot and thus its requests get counted. It seems that this is because the removed check for Mozilla in the user agent.
Regression form #125
We should either re-add a reasonable whitelist or add “check“ and/or “monitor“ to the blacklist. Sounds familiar from Nagios/Icinga modules...
Btw. PRTG Monitoring add this line: Mozilla/5.0 (compatible; PRTG Network Monitor (www.paessler.com); Windows)
So +1 for “monitor“. This would have passed the 1.6 whitelist (Windows, Mozilla).
For dynamic user-defined blacklists there is an extension-plugin Statify Blacklist (disclaimer: my plugin). You can at least temporarily block the Monitoring IPs (UA is on my wishlist).
We might discuss whether to merge both functionalities into Statify in future releases.
Until then you can only utilize a custom statify__skip_tracking Hook...
I noticed that there are many more visitors on my website since v1.7.0. This seems cool, but I was a little bit pessimistic and thus looked into the server logs.
I noticed that the Icinga uptime check is no more recognised as bot and thus its requests get counted. It seems that this is because the removed check for
Mozilla
in the user agent.This is a request:
It would be nice to have such identifiers also in the
is_bot()
method.And it would be also nice to be able to filter these identifiers to add/remove them depending on your need.
The text was updated successfully, but these errors were encountered: