4 ms·
I have at least one datapoint to suggest that people are looking for this kind of thing. I run a service, Cronitor, essentially a dead man's switch for jobs, h
by encoderer 10y ago
I have at least one datapoint to suggest that people are looking for this kind of thing.
I run a service, Cronitor, essentially a dead man's switch for jobs, heartbeats, etc. Doing some analysis on notification method preferences (Email is top, followed by Slack) I noticed a webhook that will hit a url that ended with send_secrets.php if the creator doesn't ping at least once every day.
No alerts had yet been sent so the secrets seem to be safe. I added a todo for a couple more test cases around alert sending -- I'd hate to ship a bug that accidentally sends whatever the heck is in that file. I would suspect the creators of this service will feel that same pressure soon.
- StavrosK 10y ago> I would suspect the creators of this service will feel that same pressure soon. The service has been running for eight or so years now, and the safeguards against this have worked pretty well, but yeah, every change is a chance for something to go wrong. I have extensive tests for the sending code and the logic to check whether it's time to send, though.
- encoderer 10y agoI would imagine you have a low number of alerts sent every day, even after 8 years? Or do you have enough noise from trialers that it would prohibit a manual review step? Early on we would basically get cc'd on every alert sent -- had to stop that by the 3rd month because jobs/services/etc actually fail all the fricken time.
- StavrosK 10y agoI did have that in the beginning, I stopped it when erroneous emails fell to zero. Extensive testing helped greatly with that, and the service had barely any false positives even in the beginning.
- pavel_lishin 10y agoI wonder what happens when a search engine finds it.