Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Docs for new comers: Calling side of django-watchman #97

Open
guettli opened this issue Feb 2, 2017 · 7 comments
Open

Docs for new comers: Calling side of django-watchman #97

guettli opened this issue Feb 2, 2017 · 7 comments

Comments

@guettli
Copy link

guettli commented Feb 2, 2017

I think it would help new comers, if you could tell some words about the "calling side" of django-watchman. I mean the client which calls the http end point and which collects and acts on the reported status messages.

I know that this is not the job of django-watchman, but it helps new comers to understand the big picture.

@mwarkentin
Copy link
Owner

@guettli Thanks for the suggestion! I agree that this would be really helpful - it would be nice to have configuration instructions for pingdom, panopta, and so on.

If I have some time I'll try to add some documentation, and of course contributions are always welcome!

@stale
Copy link

stale bot commented Jan 30, 2018

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale label Jan 30, 2018
@guettli
Copy link
Author

guettli commented Jan 31, 2018

I know that new features look far more appealing than new comer friendly docs. Nevertheless I still think that new comer friendly docs containing a "big picture" are the key to success.

@mwarkentin
Copy link
Owner

@guettli I have to agree with you there - I've made sure this issue won't be closed as stale. Any chance you're interested in helping to get that sort of doc started? Even a rough outline of what you think the main pieces might be would be helpful.

@guettli
Copy link
Author

guettli commented Jan 31, 2018

@mwarkentin thank you for looking at this issue again. Up to now I don't use django-watchman since we have not decided which tool we want to use to collect the results. That's why I am curious what you suggest :-)

@mwarkentin
Copy link
Owner

Ok makes sense. Personally I’ve used both Pingdom and more recently Panopta. Both have worked well for us.

Seems like it would make sense to have an “integrations” section to the doc where it could walk through the configuration for various services.

@mwarkentin
Copy link
Owner

mwarkentin commented Feb 28, 2022

Some integrations we could document:

Start monitoring in 30 seconds. Use advanced SSL, keyword and cron monitoring. Get notified by email, SMS, Slack and more. Get 50 monitors for FREE!
StatusCake
Website Monitoring solution that drives revenue & keeps you online. Track your uptime, page speed, domain, server, & SSL certificates.
pingdom.com
We help you gain instant insights into your website’s availability and performance so that you can outsmart competition with an amazing end-user experience.
Panopta
Empower your organization with centralized IT operations management. Eliminate IT tool sprawl with monitoring, incident response and automation in one platform.
ϟ Website monitoring — beautiful, simple and inexpensive.
Monitor and understand your critical cron jobs, background tasks, websites, APIs and more. Instant alerts when something goes wrong. Free 14 day trial.
Radically better uptime monitoring platform with phone call alerts, status pages, and incident management built-in. Free plan included!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants