본문으로 건너뛰기
버전: dev

Monitoring HertzBeat

Monitor the status, internal queues, JVM threads, and JVM memory of a HertzBeat server through its HTTP APIs and Actuator endpoints.

Prerequisites​

  • The collector assigned to this monitor must be able to access the target HertzBeat server.
  • Prepare an account that can access the HertzBeat summary, internal metrics, and Actuator metrics endpoints.
  • If HTTPS is enabled on the target server, enable HTTPS in the monitor and use the corresponding HTTPS port.

The monitor collects data from /api/summary, /api/metrics, and the JVM metrics exposed under /actuator/metrics.

Configuration parameters​

Parameter nameParameter description
Target HostIPv4 address, IPv6 address, or domain name of the HertzBeat server. Do not include http:// or https://.
Monitoring nameUnique name used to identify this monitor.
PortPort of the HertzBeat server. The default port is 1157.
Enable HTTPSWhether to access the target server through HTTPS.
TimeoutMaximum time in milliseconds to wait for an HTTP response. The default value is 6000.
Auth TypeHTTP authentication type. The template supports Basic Auth and Digest Auth.
UsernameUsername used to access the protected HertzBeat API and Actuator endpoints.
PasswordPassword used to access the protected HertzBeat API and Actuator endpoints.
CollectorCollector used to schedule data collection for this monitor.
Collection intervalInterval between data collections, in seconds. The minimum interval is 30 seconds.
Bind tagsTags used to categorize and manage the monitored resource.
DescriptionAdditional information about the monitor.

Collection metrics​

Metric set: Summary​

Provides an overview of the monitor types managed by the target HertzBeat server.

Metric nameUnitDescription
appNoneMonitor application type.
categoryNoneMonitor category.
statusNoneStatus of the monitor application type.
SizeNoneTotal number of monitors for this type.
availableSizeNoneNumber of available monitors for this type.

Metric set: Inner Queue​

Provides the current sizes of HertzBeat internal data queues.

Metric nameUnitDescription
responseTimemsResponse time of the internal metrics endpoint.
alertDataQueueNoneNumber of entries in the alert data queue.
metricsDataToAlertQueueNoneMetrics waiting to be processed by the alerter.
metricsDataToPersistentStorageQueueNoneMetrics waiting for persistent storage.
metricsDataToMemoryStorageQueueNoneMetrics waiting for in-memory storage.

Metric set: Threads​

Provides the number of JVM threads in each thread state.

Metric nameUnitDescription
stateNoneJVM thread state.
numberNoneNumber of threads in this state.

Metric set: Memory Used​

Provides JVM memory usage grouped by memory space.

Metric nameUnitDescription
spaceNoneJVM memory space name.
mem_usedMBMemory used in this space.

Troubleshooting​

  • If collection returns 401 or 403, verify the authentication type, username, password, and account permissions.
  • If JVM thread or memory metrics cannot be collected, verify that the target server exposes the required Actuator metrics endpoints.
  • When using a remote collector, do not use localhost unless HertzBeat is running on the same host as that collector.