Skip to content

Aerospike Monitoring v2.8.0
Compare
Choose a tag to compare
@mphanias mphanias released this 20 Sep 17:12
v2.8.0
da6dde6
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

Description

NOTE: The v2.8.0 Grafana dashboards are not backwards compatible with servers older than 6.0.0.0.

  • This release includes 1 major feature - Connector Dashboard, Alerts and topology.
  • Aerospike Monitoring Stack version 2.8.0 adds 2 dashboard, alerts and bug fixes:
    • 2 dashboards to monitor connectors and connector JVM metrics.
    • Enhanced alerts to cover various aspects of Connector key metric thresholds and JVM health.

NOTE:

  • Aerospike Prometheus exporter 1.13.0 or greater must be used to get the Aerospike 6.4 metrics.
  • The Multi-Cluster View dashboard now requires the Diagram Panel plugin.

Features

  • [OM-64] - Create predefined Prometheus alert rules for Connectors.
    • This release include 6 alerts to cover mandatory functional and process/health of the Connectors.
      • Key alerts covered are connector-status, connector-request-lag, connector-request-errors, jvm heap, jvm cpu and jvm gc.
  • [OM-56] - Connectors alerts & Dashboards
    • Connector view dashboard which helps to monitor 6 connectors.
      • Connectors supported are - xdr-proxy, kafka-outboud, pulsar-outbound, esp-outbound, elastic-search and jms-outbound.
      • Key metrics covered are - request lag, request error, success, skipped, connections, xdr record byte size, etc....
  • [OM-107] - Create a dashboard for a Connector(s)
    • Connector JVM view dashboard which helps to monitor JVM health of 6 Connectors.
      • Connectors supported are - xdr-proxy, kafka-outboud, pulsar-outbound, esp-outbound, elastic-search and jms-outbound.
      • Key metrics covered are - uptime, cpu, memory, threads, files, classes and buffers.
    • Multi-cluster view dashboard is enhanced to display Aerospike Server topology using the cluster-name and xdr dc configurations.
      NOTE:
      • To view data replication topology in multi-cluster-view.
      • The cluster-name is mandatory and destination cluster-name is configured as the name of dc in xdr section of the Aerospike Server configuration.

Fixes

  • [OM-122] - Avoid duplicate defrag metric values on the namespace dashboard.
  • [OM-113] - Namespace view dashboard - average objects per sprig stat.
  • [OM-120] - Add high-water mark breached to the Rolling Restart dashboard.
Assets 2
Loading