The discussion revolves around making the crawler/anon/logged-in toggle on the dashboard graph more discoverable. CubeCoders highlights that crawler traffic overwhelms user data, rendering the graph ineffective for analyzing real user behavior. JammyDodger shares a solution via a hidden toggle feature, which CubeCoders finds useful but notes is not intuitive due to lack of visual cues. JammyDodger agrees that clearer interaction indicators would help, admitting they only learned about the feature through a community post. mattdm questions whether the high crawler count is due to excessive bot activity, and CubeCoders explains that their uptime monitoring tool (Uptime Robot) is the main source, with many requests having no specified user agent. Julien_Palard appreciates the toggle but suggests it should persist across page reloads for usability.
Even though the pageviews for users is in the thousands, they are dwarfed by the number of page views for crawlers. The result is that the graph in the community help section is basically useless because the information I care about the most is too small to see:
Aah that’d do it! It’s not very discoverable though - I’d expect the cursor to change to the hand-pointer for elements that are interactable in the absence of a label.
I think an extra clue that it was an interactive toggle would be good. I have to shamefully admit that I did not know about it until @merefield pointed it out.
The uptime monitoring solution we use (uptime robot) is identified as a crawler, which is checking the page once per minute. It features dominantly in the statistics.
Indeed it might be nice to have a way to separate out User agents that are part of known non-crawler services that provide other facilities.
Edit: The most prevalent user agent though appears to just be “—” which I’m assuming is “No user agent speciffied” ?