diff --git a/proto/opamp.proto b/proto/opamp.proto
index 8aeae6c..5cf2a5f 100644
--- a/proto/opamp.proto
+++ b/proto/opamp.proto
@@ -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.
+    // Attributes are component specific and outside the concerns of the OpAMP protocol.
+    // Status: [Development]
+    repeated KeyValue attributes = 7;
 }
 
 message EffectiveConfig {
diff --git a/specification.md b/specification.md
index 9e0443a..2c55526 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<string, ComponentHealth> component_health_map = 6;
+    repeated KeyValue attributes = 7;
 }
 ```
 
@@ -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: