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
leader election receiver takes the input from the defined config file
When the leader election is won the sub-receiver starts and when it looses the sub-receiver stops
The sub-receiver that has been added is k8s cluster receiver
Readme has been updated
unit tests have been added
Sub receiver metrics are present out of box eg:
otelcol_receiver_accepted_metric_points{receiver="k8s_cluster//singleton_receiver_creator",service_instance_id="d35b0935-4f95-4f7e-8074-89dee76a698a",service_name="kyma-otelcol",service_version="0.102.1",transport="http"} 1218
# HELP otelcol_receiver_refused_metric_points Number of metric points that could not be pushed into the pipeline.
# TYPE otelcol_receiver_refused_metric_points counter
otelcol_receiver_refused_metric_points{receiver="k8s_cluster//singleton_receiver_creator",service_instance_id="d35b0935-4f95-4f7e-8074-89dee76a698a",service_name="kyma-otelcol",service_version="0.102.1",transport="http"} 0
What is missing is metrics from singleton receiver. We can have following custom metrics:
Description
Have a first implementation of a decorating receiver, which will activate a nested receiver on if it got selected as leader in a leader election mechanism, see also https://github.com/kyma-project/telemetry-manager/blob/main/docs/contributor/arch/012-leader-receiver-creator.md
A dummy implementation can be found here: https://github.com/skhalash/leaderreceivercreator
Criterias
Reasons
Attachments
The text was updated successfully, but these errors were encountered: