-
|
Hello, |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
|
Hi, That is by design. All observers store their monitoring data in instances of the same type, TelemetryData. For NodeObserver, there is no ApplicationName or ServiceName (or Partition or Replica) associated with what it monitors: machine-level resource usage across various metrics. Only AppObserver would have these properties set in the instances of TelemetryData it creates. What you see in the Description field is a JSON-serialized instance of TelemetryData. |
Beta Was this translation helpful? Give feedback.
-
|
You'll notice in the latest releases that node telemetry only contains related fields (same for Disk). Gone are the days of null noise. |
Beta Was this translation helpful? Give feedback.
Hi,
That is by design. All observers store their monitoring data in instances of the same type, TelemetryData. For NodeObserver, there is no ApplicationName or ServiceName (or Partition or Replica) associated with what it monitors: machine-level resource usage across various metrics. Only AppObserver would have these properties set in the instances of TelemetryData it creates.
What you see in the Description field is a JSON-serialized instance of TelemetryData.