-
Notifications
You must be signed in to change notification settings - Fork 62
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
Comments
@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! |
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. |
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. |
@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. |
@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 :-) |
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. |
Some integrations we could document:
|
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.
The text was updated successfully, but these errors were encountered: