jmx-monitoring-stacks
jmx-monitoring-stacks copied to clipboard
confluentinc
📊 Monitoring examples for Confluent Cloud and Confluent Platform
Corrected password for grafana in README to the same password as in compose file.
ksql_ksql_metrics_ksql_queries_query_status  
Major change to manage grafana dashboards via scripts, using [grafanalib](https://grafanalib.readthedocs.io/en/stable/index.html). Changes: - New directory for dashboard scripts: ./grafana-dashboards - Script to generate dashboards for VM/cp-demo deployments and CFK deployments: ./grafana-dashboards/Makefile...
We have a kafka cluster of 5 brokers. And have setup cluster linking with the DR environment. Want to setup grafana dashboard for cluster linking so that we can pull...
Using this jmx_exporter config [https://github.com/confluentinc/jmx-monitoring-stacks/blob/6.1.0-post/shared-assets/jmx-exporter/kafka_broker.yml](url) Get metrics from url takes 3 minutes ! How it is possible to use by anyone for any cluster? In what case could it be...
In the grafana dashboard for Zookeeper, I see that the latency metrics are being [multiplied by zookeeper ticktime](https://github.com/confluentinc/jmx-monitoring-stacks/blob/98e16b4f26f052c61152909f4a452c85d223dd43/jmxexporter-prometheus-grafana/assets/grafana/provisioning/dashboards/zookeeper-cluster.json#L894). This has the effect of multiplying ZK request latency by 3000 (the...
When running on WSL2 on Windows, Metricbeat container will not start with error `Exiting: error loading config file: config file ("metricbeat.yml") can only be writable by the owner but the...
After importing JMX exporter config file, I couldnt find kafka_connect_cluster_id metric under the metric key kafka_connect_app_info. This is showing only below mentioned metrics. kafka_connect_app_info{start_time_ms="1652081661119",client_id="connect-1",job="kafka-connect"} 1.0 kafka_connect_app_info{commit_id="c6d7e3013b411760",client_id="connect-1",job="kafka-connect"} 1.0 kafka_connect_app_info{version="7.0.0-ccs",client_id="connect-1",job="kafka-connect"} 1.0
Should this be a multiple of 100 to better correlate the metrics to the actual cores available on the server? [connect-overview.json](https://github.com/confluentinc/jmx-monitoring-stacks/blob/6.0.1-post/jmxexporter-prometheus-grafana/assets/prometheus/grafana/provisioning/dashboards/connect-overview.json) rate(process_cpu_seconds_total{job="connect",env="$env",cluster=~"$cluster",instance=~"$instance"}[5m])*100
Metadata
Owner
Metadata
📊 Monitoring examples for Confluent Cloud and Confluent Platform