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

server should monitor and report events #29

Open
ssfrr opened this issue Oct 8, 2014 · 2 comments
Open

server should monitor and report events #29

ssfrr opened this issue Oct 8, 2014 · 2 comments

Comments

@ssfrr
Copy link
Member

ssfrr commented Oct 8, 2014

we have a graphite instance running to track basic system stats (hard drive space CPU usage, etc.), and a statsd server so it's easy to pump new data in. I'd like to start keeping track of the rate new data is coming in, error rates, etc.

@kkleidal
Copy link
Contributor

This seems like a good task for a "topics" network flow: whenever a request is made/data is posted, we could call a method which writes the event details to a websockets (or ZMQ) stream with a tag. Then, we could have an analyzer microservice monitoring the stream and logging as necessary.

@ssfrr
Copy link
Member Author

ssfrr commented Feb 16, 2015

I think it's even easier than that. We already have the graphite instance up and receiving data, so all we need to do us use a statsd client from python to pump metrics in.

Statsd works with a tagging system sort of like what you're describing so you can label your metrics, but we can just instrument the code so that we send the event signal when the things we're tracking happen. It sends over UDP so it doesn't really add overhead even if the receiving server goes down.

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