# Consolidated Pageviews: exclude uptime crawler from report without blocking?

**URL:** https://meta.discourse.org/t/consolidated-pageviews-exclude-uptime-crawler-from-report-without-blocking/323848
**Category:** Support
**Tags:** dashboard-reports
**Created:** [August 28, 2024, 6:59pm UTC](https://meta.discourse.org/t/consolidated-pageviews-exclude-uptime-crawler-from-report-without-blocking/323848 "2024-08-28T18:59:49Z")
**Posts on this page:** 6
**Page:** 1

<div class="post-metadata">

### Author: ![ToddZ](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/toddz/32/328350_2.png) [@ToddZ](https://meta.discourse.org/u/ToddZ)
#### Post date: [August 28, 2024, 6:59pm UTC](https://meta.discourse.org/t/consolidated-pageviews-exclude-uptime-crawler-from-report-without-blocking/323848/1 "2024-08-28T18:59:49Z")

</div>

So I’ve set up an instance of [Uptime Kuma](https://github.com/louislam/uptime-kuma) to monitor my forum, and now, of course, the crawler graph has skyrocketed. I know I can [toggle crawlers](https://meta.discourse.org/t/anyway-to-disable-crawlers-in-consolidated-pageview/200657/2) entirely from the display by clicking “Crawlers” in the graph key, but I’d like to _just_ exclude the “Uptime-Kuma” user agent behind the scenes and still watch for other spikes.

(@pfaffman – [you’ve brought this up before](https://meta.discourse.org/t/consolidated-pageviews-accuracy/107193/17) – did you happen to come up with anything?)

---

<div class="post-metadata">

### Author: ![pfaffman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pfaffman/32/120154_2.png) [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [August 28, 2024, 7:05pm UTC](https://meta.discourse.org/t/consolidated-pageviews-exclude-uptime-crawler-from-report-without-blocking/323848/2 "2024-08-28T19:05:22Z")

</div>

> [@ToddZ](#):
>
> (@pfaffman – [you’ve brought this up before](https://meta.discourse.org/t/consolidated-pageviews-accuracy/107193/17) – did you happen to come up with anything?)

You can hit `/srv/status` and that doesn’t get counted. You might also be able to hit something like `/t/-/123.json` and then look for `title` or something like that. I think that won’t count as a pageview.

---

<div class="post-metadata">

### Author: ![ToddZ](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/toddz/32/328350_2.png) [@ToddZ](https://meta.discourse.org/u/ToddZ)
#### Post date: [August 28, 2024, 7:59pm UTC](https://meta.discourse.org/t/consolidated-pageviews-exclude-uptime-crawler-from-report-without-blocking/323848/3 "2024-08-28T19:59:14Z")

</div>

> [@pfaffman](#):
>
> You can hit `/srv/status` and that doesn’t get counted.

**Thank you Jay!** I’ve added that to the tracking URL, and it appears to have stopped adding to the crawler count.

I forgot to mention that prior to this I’ve had [Uptime Robot](https://uptimerobot.com/) in place for a long time, just tracking the base URL.

Interestingly, YTD Discourse has reported _just 1 hit_ from `Mozilla/5.0+(compatible; UptimeRobot/2.0; http://www.uptimerobot.com/)`.

I wonder if some uptime crawlers are automatically excluded from reporting..? 🤔

---

<div class="post-metadata">

### Author: ![pfaffman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pfaffman/32/120154_2.png) [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [August 28, 2024, 8:11pm UTC](https://meta.discourse.org/t/consolidated-pageviews-exclude-uptime-crawler-from-report-without-blocking/323848/4 "2024-08-28T20:11:38Z")

</div>

> [@ToddZ](#):
>
> **Thank you Jay!** I’ve added that to the tracking URL, and it appears to have stopped adding to the crawler count.

Glad to hear it.

There are some cases where `/srv/status` can say ‘ok’ when it’s not so OK. I think there’s a communiteq plugin that catches some more cases, but I couldn’t find it in 10 seconds.

> [@ToddZ](#):
>
> I wonder if some uptime crawlers are automatically excluded from reporting…? 🤔

I don’t see `UptimeRobot` in the source. And I’m pretty sure that I remember UptimeRobot hits counting at some time in the past, but I’ve been using `/srv/status` for a long time.

---

<div class="post-metadata">

### Author: ![RGJ](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/rgj/32/523185_2.png) [@RGJ](https://meta.discourse.org/u/RGJ)
#### Post date: [August 29, 2024, 4:29pm UTC](https://meta.discourse.org/t/consolidated-pageviews-exclude-uptime-crawler-from-report-without-blocking/323848/6 "2024-08-29T16:29:00Z")

</div>

> [@pfaffman](#):
>
> I think there’s a communiteq plugin that catches some more cases, but I couldn’t find it in 10 seconds.

I forgot about that !!! And I had to look for it for over 10 minutes as well.

It’s here [GitHub - communiteq/discourse-betterstatus · GitHub](https://github.com/communiteq/discourse-betterstatus) and TBH I have no idea if it still works. If it does, it will perform a very rudimentary check to see if Redis and Postgres are working.

---

<div class="post-metadata">

### Author: ![system](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/system/32/443519_2.png) [@system](https://meta.discourse.org/u/system)
#### Post date: [October 9, 2024, 5:46am UTC](https://meta.discourse.org/t/consolidated-pageviews-exclude-uptime-crawler-from-report-without-blocking/323848/7 "2024-10-09T05:46:00Z")

</div>

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
