carbon-relay-ng
carbon-relay-ng copied to clipboard
grafana
Configurable route plugins? [Sumo Logic]
Greetings,
Looking over the architecture and features of carbon-relay-ng. There are multiple supported route types out of the box. Are routes designed to be extensible? Meaning, can carbon-relay-ng routes support be extended?
The use case I'm looking at is that I have an application that supports Graphite format metrics and can emit metrics to a Graphite (Carbon) installation, but I don't operate Graphite. I currently do all metrics collection with collectd and a plugin for streaming metrics to Sumo Logic (SaaS). I need something that can take in Graphite metrics and relay them to Sumo Logic, and a router/proxy like carbon-relay-ng seems feasible, if it could be extended with a module for routing to Sumo.
https://help.sumologic.com/03Send-Data/Sources/02Sources-for-Hosted-Collectors/HTTP-Source/Upload-Metrics-to-an-HTTP-Source
the route system is extensible, but would require code changes to the main project and the routes would have to be compiled in. the main concern then would be who will maintain such plugins over time.
Is a change possible to decouple extensible portions of the system more fully? They could be entirely separate projects using an interface and supported in full by outside contributors in that case.
On Tue, Feb 9, 2021 at 9:55 AM Dieter Plaetinck [email protected] wrote:
the route system is extensible, but would require code changes to the main project and the routes would have to be compiled in. the main concern then would be who will maintain such plugins over time.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/grafana/carbon-relay-ng/issues/453#issuecomment-776083701, or unsubscribe https://github.com/notifications/unsubscribe-auth/AA66EQIKJGD5J57DJQWSWELS6FSJHANCNFSM4XJ4WV3Q .
-- Darren Spruell [email protected]