Skip to content

[Feat]: reduce number of endpoints for monitoring components #106

@dmitry618

Description

@dmitry618

Is your feature request related to a problem? Please describe

Both QubershipPrometheusRecordSink and ComponentPrometheusReportingTask are creating their own server to handle metric scraping requests from Prometheus or other compatible tool. This wastes system resources.

Describe the solution you'd like

Both QubershipPrometheusRecordSink and ComponentPrometheusReportingTask and any other similar components should use single endpoint, provided by some other component (probably controller service) to expose their metrics.

Backward compatibility must be maintained, i.e. we should keep options for hostname/port, but probably make them optional and add new optional controller service reference for new functionality.

Describe alternatives you've considered

No response

Additional information

No response

Metadata

Metadata

Labels

enhancementNew feature or request

Projects

Status

Ready

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions