thank you!

[dylang]

Not a bug, just a thanks!

I was thinking about building this after being underwhelmed with nopents, but what you built looks way more impressive than what I could have done.

Thank you!

For use in the browser, use browserify.

👍 awesome!

[dylang]

This is the kind of problem I hope to use opentsdb.js to solve: GoogleChromeLabs/psi#10

[kgryte]

@dylang Thanks for the comment. I, too, was underwhelmed with the OpenTSDB clients available, which is why I wrote my own.

And yes, totally, OpenTSDB is certainly one possibility for storing application performance metrics. I have also seen OpenTSDB and Elasticsearch integration, which allows for enhanced search. I will be curious to see what you settle on for a final solution.

One drawback currently is that this library is currently read-only. I have yet to implement put requests. This is straightforward and on the roadmap for later this week. Some libraries use the REST interface for saving data in OpenTSDB. This is not performant. If you need to pipe data into OpenTSDB and time is of the essence, be sure to use a library which creates a socket connection and pipes from there. The performance gains are significant.

[kgryte]

A socket client is now included with the library, thus allowing writing to OpenTSDB. Closing this issue.