Skip to content

Add ComponentHealth.attributes#334

Open
michel-laterman wants to merge 1 commit into
open-telemetry:mainfrom
michel-laterman:enhancement/add-componenthealth-attributes
Open

Add ComponentHealth.attributes#334
michel-laterman wants to merge 1 commit into
open-telemetry:mainfrom
michel-laterman:enhancement/add-componenthealth-attributes

Conversation

@michel-laterman
Copy link
Copy Markdown
Contributor

Add attributes in order to be consistent with what the healthcheck extension produces. See extension source.

@michel-laterman michel-laterman requested a review from a team as a code owner May 12, 2026 16:28
Copy link
Copy Markdown
Member

@tigrannajaryan tigrannajaryan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What are "attributes" supposed to carry? We need a more elaborate motivation before accepting this change.

Looking at the extension event, it says "attributes provides additional context or metadata for the event" which is very vague to me.

@michel-laterman
Copy link
Copy Markdown
Contributor Author

For example the attributes of a hostmetrics scraper can include things to indicate specifics on which scrapers are failing, as seen in the extension issue is:

    "pipeline:metrics/1": {
      "healthy": true,
      "status": "StatusRecoverableError",
      "status_time": "2025-10-16T17:56:11.820542393+02:00",
      "attributes": {
        "error_msg": "not enough permissions to read cpu data",
        "scrapers": ["cpu", "memory", "network"]
      },

extension implementation pr.

It could further be used to indicate other metadata such as port numbers, address, etc.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Add attributes to ComponentHealth messages

2 participants