From 1afe354b13b7f3e9b0b521880f9421ae0b9b75c6 Mon Sep 17 00:00:00 2001 From: michel-laterman Date: Tue, 12 May 2026 18:27:16 +0200 Subject: [PATCH 1/3] Add ComponentHealth.attributes --- proto/opamp.proto | 3 +++ specification.md | 6 ++++++ 2 files changed, 9 insertions(+) diff --git a/proto/opamp.proto b/proto/opamp.proto index 8aeae6c..658b911 100644 --- a/proto/opamp.proto +++ b/proto/opamp.proto @@ -810,6 +810,9 @@ message ComponentHealth { // A map to store more granular, sub-component health. It can nest as deeply as needed to // describe the underlying system. map component_health_map = 6; + + // Additional context or metadata for the observed component's status. + repeated KeyValue attributes = 7; } message EffectiveConfig { diff --git a/specification.md b/specification.md index 9e0443a..45b8d9f 100644 --- a/specification.md +++ b/specification.md @@ -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) @@ -1242,6 +1243,7 @@ message ComponentHealth { string status = 4; fixed64 status_time_unix_nano = 5; map component_health_map = 6; + repeated KeyValue attributes = 7; } ``` @@ -1275,6 +1277,10 @@ 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. + #### EffectiveConfig Message The EffectiveConfig message has the following structure: From 1827077681c0dbfca626b1836474e1cb14841ef7 Mon Sep 17 00:00:00 2001 From: michel-laterman Date: Tue, 2 Jun 2026 13:43:15 -0700 Subject: [PATCH 2/3] Add comment to state that attributes are component specific --- proto/opamp.proto | 1 + specification.md | 1 + 2 files changed, 2 insertions(+) diff --git a/proto/opamp.proto b/proto/opamp.proto index 658b911..5b42e1d 100644 --- a/proto/opamp.proto +++ b/proto/opamp.proto @@ -812,6 +812,7 @@ message ComponentHealth { map component_health_map = 6; // Additional context or metadata for the observed component's status. + // Attributes are component specific and outside the concerns of the OpAMP protocol. repeated KeyValue attributes = 7; } diff --git a/specification.md b/specification.md index 45b8d9f..2c55526 100644 --- a/specification.md +++ b/specification.md @@ -1280,6 +1280,7 @@ 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 From 0accc67d61bc5b1ede8f2abb2f679ce802e3d915 Mon Sep 17 00:00:00 2001 From: michel-laterman Date: Fri, 5 Jun 2026 15:50:29 -0700 Subject: [PATCH 3/3] set attributes to development --- proto/opamp.proto | 1 + 1 file changed, 1 insertion(+) diff --git a/proto/opamp.proto b/proto/opamp.proto index 5b42e1d..5cf2a5f 100644 --- a/proto/opamp.proto +++ b/proto/opamp.proto @@ -813,6 +813,7 @@ message ComponentHealth { // Additional context or metadata for the observed component's status. // Attributes are component specific and outside the concerns of the OpAMP protocol. + // Status: [Development] repeated KeyValue attributes = 7; }