Apache HertzBeat™ is an AI-powered next-generation open source real-time observability system. Unified metrics and logs collection, centralized alerting distribution, intelligent management and analysis. No Agent required, high performance cluster, provides powerful custom monitoring and status page building capabilities.

• Integrates collection + analysis + alerting + notification into one platform, with new AI-powered interactions and features under HertzBeat AI, and built-in MCP Server capabilities.
• Unified metrics platform, agentless, Prometheus-compatible, supports application services, programs, databases, caches, operating systems, big data, middleware, web servers, cloud-native, networks, custom monitoring and more.
• Unified logging platform, seamlessly integrates multiple log sources through OTLP protocol for reporting.
• Unified alerting platform, integrates internal alerts with various external alert sources, unified alert processing and analysis, flexible real-time and periodic threshold rules, grouping convergence, silence, suppression, etc.
• Unified message distribution, alerts processed by the alerting platform are distributed via Email Discord Slack Telegram DingTalk WeChat FeiShu SMS Webhook ServerChan and other methods.
• Makes protocols such as Http, Jmx, Ssh, Snmp, Jdbc, Prometheus configurable, allowing you to collect any metrics by simply configuring the template YML file online. Imagine being able to quickly adapt to a new monitoring type like K8s or Docker simply by configuring online with HertzBeat.
• High performance, supports horizontal expansion of multi-collector clusters, multi-isolated network monitoring and cloud-edge collaboration.
• Provides powerful status page building capabilities, easily communicate the real-time status of your service to users.

HertzBeat's unified platform, AI intelligence, powerful customization, multi-type support, high performance, and easy expansion, aims to help users quickly and conveniently achieve observability requirements.

This Helm chart installs HertzBeat in a Kubernetes cluster. Welcome to contribute to Helm Chart for HertzBeat.

• Kubernetes cluster 1.20+
• Helm v3.2.0+

helm repo add hertzbeat https://charts.hertzbeat.apache.org/
helm repo update

The following items can be set via --set flag during installation or configured by editing the values.yaml directly (need to download the chart first).

• Ingress: The ingress controller must be installed in the Kubernetes cluster.
• ClusterIP: Exposes the service on a cluster-internal IP. Choosing this value makes the service only reachable from within the cluster.
• NodePort: Exposes the service on each Node’s IP at a static port (the NodePort). You’ll be able to contact the NodePort service, from outside the cluster, by requesting NodeIP:NodePort.
• LoadBalancer: Exposes the service externally using a cloud provider’s load balancer.

The external URL for HertzBeat core service is used to:

1. populate the docker/helm commands showed on portal
2. populate the token service URL returned to docker client

Format: protocol://domain[:port]. Usually:

• if service exposed via Ingress, the domain should be the value of expose.ingress.hosts
• if service exposed via ClusterIP, the domain should be the value of expose.clusterIP.name
• if service exposed via NodePort, the domain should be the IP address of one Kubernetes node
• if service exposed via LoadBalancer, set the domain as your own domain name and add a CNAME record to map the domain name to the one you got from the cloud provider

If HertzBeat is deployed behind the proxy, set it as the URL of proxy.

• Disable: The data does not survive the termination of a pod.
• Persistent Volume Claim(default): A default StorageClass is needed in the Kubernetes cluster to dynamically provision the volumes. Specify another StorageClass in the storageClass or set existingClaim if you already have existing persistent volumes to use.

Install the HertzBeat helm chart with a release name my-release:

helm install hertzbeat hertzbeat/hertzbeat

To uninstall/delete the hertzbeat deployment:

helm uninstall hertzbeat

The following table lists the configurable parameters of the HertzBeat chart and the default values.
Config Parameter via --set, eg: --set expose.type=NodePort

1. helm package charts/* -d docs
2. helm repo index docs
3. commit and pr change

1. cd charts
2. helm template --debug hertzbeat
3. helm upgrade --set expose.type=NodePort --install demo ./hertzbeat
4. helm uninstall demo