If we want to measure and log "real" pageviews from out Confluence, see Access Logging in Confluence, and we a not doing this from within Confluence, we need to filter out false results.

this This is my current filterring Resultsfindings regarding to filtering results:

Robots and Crawlers

We need to filter out those:

...

uri="*/display/*" OR uri="*/viewpage.action/*"

Monitoring

Monitoringring on Monitoring a website from various Souces (Zenoss, Nagios, Datadog etc etc) also represents a large (often the largest) number of hits, and we need to remove these, this can be done is several ways:

• Identifying all agent types of the monitoring
• Often monitoring is on / - giving the agent a HTTP Code 302 back code. This is not the case for mysite, where apache makes a rewrite; hence the monitoring gets a HTTP Code 200 OK
  

Looking into You logs will often make it pretty easy to Identify monitoring:

...

Here its my datadog monitoring from another server:

Image Added

And from Worldping via Grafana:

Image Added