You know who bots are because they only see non-JavaScript pages?
Perhaps bots for free and increase user request prices appropriately?
At the moment the only egregious bot we are seeing is actually one we are running to ensure sites are up and running, we test each site we run 3 times a minute and it adds up to quite a high number. So we will add a specific ignore for it in our custom plugin.
2개의 좋아요
Actually I run Pingdom against a few of my Discourse instances and would benefit from a similar plugin.
Is this something that would be “easy” for you to open source?
If not don’t worry - I’m sure you have enough to do.
1개의 좋아요
Actually leaning on just using a our custom header for this,
If Discourse-Track-View is false or 0 do not count. Does pingdom allow you to inject headers?
Yes:
4개의 좋아요
This is now implemented per:
https://github.com/discourse/discourse/commit/cbe18eb0dfb8063251d2b3f18d4a326464ef3e1b
3개의 좋아요
Soo .. how about simplifying this even more ..?
Skip the traffic metric and base your pricing on # of users..
(I used dev tools to remove the traffic and just have limit on users)
1개의 좋아요
Thanks @sam! - updated my pingdom monitoring…
… not sure where to look to make sure it’s working - I’m sure some numbers in admin will decrease over the next couple of days.
1개의 좋아요
From our experience the vast majority of traffic sites get are from anon, you have to factor that in.
2개의 좋아요
No, I don’t support limiting by number of users at all. Violently opposed. The whole point of Discourse is to build a large community. What if you have 100,000 users but only 1,000 show up every day? That’s what we want to measure and charge for, and that is activity aka “API views”.
Not to mention anons as @sam noted.
3개의 좋아요
These stats are now visualised as well!
3개의 좋아요