From 7cb4ecc9f82a96a2e3605cac7bb4d885dd80d4c8 Mon Sep 17 00:00:00 2001 From: Jacob Aronoff Date: Tue, 7 May 2024 16:40:49 -0400 Subject: [PATCH] Apply suggestions from code review Co-authored-by: Matthew Wear --- proto/opamp.proto | 2 +- specification.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/proto/opamp.proto b/proto/opamp.proto index c15c2d7..7a34311 100644 --- a/proto/opamp.proto +++ b/proto/opamp.proto @@ -271,7 +271,7 @@ message OpAMPConnectionSettings { // // A Polling-based HTTP Client MUST use the value as polling interval. // - // A heartbeat is used to keep a load balancer connection active AND inform the server that the Agent + // A heartbeat is used to keep a load balancer connection active and inform the server that the Agent // is still alive and active. // // This field is optional: diff --git a/specification.md b/specification.md index c3a9566..3967ddb 100644 --- a/specification.md +++ b/specification.md @@ -1867,7 +1867,7 @@ message. At a minimum the instance_uid field MUST be set. It is recommended that also set ComponentHealth as well. An HTTP based-client MUST use the heartbeat interval as its polling interval. -A heartbeat is used to keep a load balancer connection active AND inform the server that +A heartbeat is used to keep a load balancer connection active and inform the server that the Agent is still alive and active. A server could use the heartbeat to make decisions about the liveness of the connected Agent.