Failover Count Metric

[akats7]

Component(s)

connector/failover

Is your feature request related to a problem? Please describe.

Creating an issue to track this work, it would be extremely useful to have a metric tied to failover count between levels of the failover connector. Extracting this info in the current state would likely require parsing log messages and would need to be custom depending on components used.

Emitting a failover count metric would be a significant benefit for maintaining long term resiliency of the collector export pipeline, as high failover counts likely point to downstream resiliency issues.

Describe the solution you'd like

Create a failover count metric similar to other collector components e.g., otelcol_processor_incoming_items for resourceprocessor, otelcol_processor_dropped_metric_points for memorylimiter, etc.

Describe alternatives you've considered

No response

Additional context

No response

[github-actions]

Pinging code owners for connector/failover: @akats7 @djaglowski @fatsheep9146. See Adding Labels via Comments if you do not have permissions to add labels yourself.

[djaglowski]

This makes sense to me. @akats7 should I assign it to you?

[akats7]

Yep thanks

[github-actions]

This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

Pinging code owners:

• connector/failover: @akats7 @fatsheep9146

See Adding Labels via Comments if you do not have permissions to add labels yourself.

[akats7]

Will address shortly