You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 25, 2023. It is now read-only.
The Prometheus format is available and works really well. To elevate ccloudexporter as the de-facto for gathering CCloud metrics instead of relying on multiple different solutions, I want to propose adding a Kafka Sink to the code base.
The defaults don't need to change at all, but if we can provide a Kafka sink, it would provide customers an option to stream the data to Kafka. For customers already streaming metrics from Kafka to an end system, this means only adding topic name to the sink connector config to stream API data from Kafka as well.
P.S: I do understand that keeping data of the system being monitored onto the system itself is an anti-pattern, but if we can give a choice, a lot of customers might like it.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The Prometheus format is available and works really well. To elevate ccloudexporter as the de-facto for gathering CCloud metrics instead of relying on multiple different solutions, I want to propose adding a Kafka Sink to the code base.
The defaults don't need to change at all, but if we can provide a Kafka sink, it would provide customers an option to stream the data to Kafka. For customers already streaming metrics from Kafka to an end system, this means only adding topic name to the sink connector config to stream API data from Kafka as well.
P.S: I do understand that keeping data of the system being monitored onto the system itself is an anti-pattern, but if we can give a choice, a lot of customers might like it.
The text was updated successfully, but these errors were encountered: