Collection and sampling as a separate library

[geostarling]

Hi,

I'm interested in using rezolus as an agent in an event-driven, push-model monitoring infrastructure that is based on Riemann as an metrics stream processor.

My requirements are as follows:

• being able to send metrics gathered by rezolus to Riemann API, either directly via Riemanns Protobuf API or indirectly through a custom HTTP gateway
• for each measurement (event) specify additional metadata, eg. host of origin, tags and other user-defined attributes (eq. unit of measurement)
• method for metadata retrieval should be extensible in the same way the samplers are right now and ideally scriptable
• support additional samplers, eg. being able to sample docker runtime metrics would be nice

It seems to me, that many of these requirements are out of scope of rezolus as it is now.

The idea is to split off collectors and sampling functionality into a library that would be not be dependent on method of telemetry publication or any other additional processing (metadata retrieval).

What is your opinion on this?

Thank you.

[brayniac]

Hi @geostarling -

I believe some of this would definitely be in-scope for the project. I plan to create some issues to track roadmap items once we've completed the current planning cycle. That should help provide some more clarity to the community.

In short, I like the idea of splitting out exposition/publication and we are actively looking into push-based publication in the near term. Metadata (particularly units) is on my wishlist too. Additional samplers, such as docket runtime metrics I believe could be implemented with things as they are today. We are definitely looking to add additional telemetry around containers.