Besides the pipeline elements (receivers, processors, and exporters) the OTelSvc uses various ad-hoc “add-on” components (e.g.: healthcheck, z-pages, etc). However, the interface and configuration for such components was not specified and the service code directly handles them individually in an ad-hoc fashion.
Design Goals:
Allow same functionality provided by the existing ad-hoc components;
Make configuration of add-ons components consistent with new model used for pipeline elements;
Make add-ons extensible in the same way as pipeline elements;
pjanotti
commented
5 years ago
Besides the pipeline elements (receivers, processors, and exporters) the OTelSvc uses various ad-hoc “add-on” components (e.g.: healthcheck, z-pages, etc). However, the interface and configuration for such components was not specified and the service code directly handles them individually in an ad-hoc fashion.
Design Goals: