Skip to content

Add ComponentHealth.attributes #334

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
michel-laterman wants to merge 3 commits into
base: main
Choose a base branch
from
+12 −0
Open

Add ComponentHealth.attributes #334

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
1afe354
Add ComponentHealth.attributes
michel-laterman May 12, 2026
1827077
Add comment to state that attributes are component specific
michel-laterman Jun 2, 2026
0accc67
set attributes to development
michel-laterman Jun 5, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions proto/opamp.proto
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -810,6 +810,11 @@ message ComponentHealth {
// A map to store more granular, sub-component health. It can nest as deeply as needed to
// describe the underlying system.
map<string, ComponentHealth> component_health_map = 6;

// Additional context or metadata for the observed component's status.
Comment thread
michel-laterman marked this conversation as resolved.
// Attributes are component specific and outside the concerns of the OpAMP protocol.
// Status: [Development]
repeated KeyValue attributes = 7;

@tigrannajaryan tigrannajaryan Jun 4, 2026

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Please mark with // Status: [Development] (see other similar fields in this proto).

}

message EffectiveConfig {
Expand Down
7 changes: 7 additions & 0 deletions specification.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -72,6 +72,7 @@ Status: [Beta]
- [ComponentHealth.status](#componenthealthstatus)
- [ComponentHealth.status_time_unix_nano](#componenthealthstatus_time_unix_nano)
- [ComponentHealth.component_health_map](#componenthealthcomponent_health_map)
- [ComponentHealth.attributes](#componenthealthattributes)
+ [EffectiveConfig Message](#effectiveconfig-message)
- [EffectiveConfig.config_map](#effectiveconfigconfig_map)
+ [RemoteConfigStatus Message](#remoteconfigstatus-message)
Expand Down Expand Up @@ -1242,6 +1243,7 @@ message ComponentHealth {
string status = 4;
fixed64 status_time_unix_nano = 5;
map<string, ComponentHealth> component_health_map = 6;
repeated KeyValue attributes = 7;
}
```

Expand Down Expand Up @@ -1275,6 +1277,11 @@ nanoseconds since 00:00:00 UTC on 1 January 1970.
A map to store more granular, sub-component health. It can nest as deeply as needed to
describe the underlying system.

##### ComponentHealth.attributes

Additional context or metadata for the observed component's status.
Attributes are component specific and outside the concerns of the OpAMP protocol.

#### EffectiveConfig Message

The EffectiveConfig message has the following structure:
Expand Down