You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: modules/get-started/pages/cloud-overview.adoc
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -99,7 +99,7 @@ Consider BYOC or Dedicated if you need more control over the deployment or if yo
99
99
100
100
* Private networking
101
101
* Multiple availability zones (AZs). A multi-AZ cluster provides higher resiliency in the event of a failure in one of the zones.
102
-
* Ability to export metrics to a 3rd-party monitoring system
102
+
* Ability to export Redpanda metrics to a third-party monitoring system
103
103
* Kafka Connect
104
104
* Higher limits and quotas. See xref:reference:tiers/byoc-tiers.adoc[BYOC usage tiers] and xref:reference:tiers/dedicated-tiers.adoc[Dedicated usage tiers] compared to xref:get-started:cluster-types/serverless.adoc#serverless-usage-limits[Serverless limits].
You can configure monitoring on your Redpanda Dedicated or BYOC cluster to maintain system health and optimize performance. Redpanda Cloud exports metrics for all brokers and Kafka Connect workers from a single Prometheus endpoint. This endpoint can be found on the *Overview* page for your cluster, under *How to connect*.
5
+
You can configure monitoring on your Redpanda BYOC or Dedicated cluster to maintain system health and optimize performance. You can monitor Redpanda with https://prometheus.io/[Prometheus^] or with any other monitoring and alerting tool, such as Datadog, New Relic, Elastic Cloud, Google Cloud, or Azure.
6
+
7
+
Redpanda Cloud exports Redpanda metrics for all brokers and connectors from a single OpenMetrics endpoint. This endpoint can be found on the *Overview* page for your cluster, under *How to connect* and *Prometheus*.
6
8
7
-
You can monitor Redpanda with Prometheus or with any other monitoring and alerting tool, such as Datadog, New Relic, Elastic Cloud, Google, or Azure.
8
9
9
10
[NOTE]
10
11
====
11
-
To maximize performance, Redpanda exports some metrics only when the underlying feature is in use. For example, a metric for consumer groups, xref:reference:public-metrics-reference.adoc#redpanda_kafka_consumer_group_committed_offset[`redpanda_kafka_consumer_group_committed_offset`], is only exported when groups are registered.
12
+
13
+
- To maximize performance, Redpanda exports some metrics only when the underlying feature is in use. For example, a metric for consumer groups, xref:reference:public-metrics-reference.adoc#redpanda_kafka_consumer_group_committed_offset[`redpanda_kafka_consumer_group_committed_offset`], is only exported when groups are registered.
14
+
- Operating system-level and node-level metrics (such as CPU, memory, disk, and network usage) are not available through this endpoint. For infrastructure monitoring, use your cloud provider's native monitoring tools (such as Azure Monitor, AWS CloudWatch, or Google Cloud Monitoring).
12
15
====
13
16
14
-
== Configure Prometheus
17
+
== Configure Redpanda monitoring
15
18
16
-
To monitor a Dedicated or BYOC cluster in https://prometheus.io/[Prometheus^]:
19
+
To monitor a BYOC or Dedicated cluster:
17
20
18
21
. On the Redpanda Cloud *Overview* page for your cluster, under *How to connect*, click the *Prometheus* tab.
19
22
20
23
. Click the copy icon for *Prometheus YAML* to copy the contents to your clipboard.
21
24
+
22
-
image::shared:cloud_metrics.png[How to connect screenshot]
23
-
+
24
25
The YAML contains the Prometheus scrape target configuration, as well as authentication, for the cluster.
25
26
+
27
+
image::shared:cloud_metrics.png[How to connect screenshot]
. Save this information to Prometheus, and observe in Prometheus that metrics from Redpanda endpoints are scraped.
42
+
. Save these settings to Prometheus or another monitoring tool, replacing the following placeholders:
43
+
+
44
+
* `<id>.<identifier>`: ID and identifier from the HTTPS endpoint.
45
+
* `<prom_pass>`: Copy and paste the onscreen Prometheus password.
46
+
40
47
41
48
== Configure Datadog
42
49
43
-
To monitor a Dedicated or BYOC cluster in https://www.datadoghq.com/[Datadog]:
44
-
45
-
. On the Redpanda Cloud *Overview* page for your cluster, under *How to connect*, click the *Prometheus* tab.
50
+
To monitor a Dedicated or BYOC cluster in https://www.datadoghq.com/[Datadog^]:
46
51
47
-
. Click the copy icon for *Prometheus YAML* to find scrape target configuration, as well as authentication, for the cluster.
52
+
. Follow the steps to configure Redpanda monitoring.
48
53
49
54
. In Datadog, define the `openmetrics_endpoint` URL for that monitored cluster. The integration configuration should look similar to the following:
50
55
+
@@ -63,7 +68,7 @@ instances:
63
68
64
69
. Restart the Datadog agent.
65
70
66
-
NOTE: Because the Prometheus endpoint in Redpanda Cloud aggregates metrics for all cluster services, only a single Datadog agent is required. The agent must run in a container in your own container infrastructure. Redpanda does not support launching this container inside a Dedicated or BYOC Kubernetes cluster. For more information, see the https://docs.datadoghq.com/integrations/redpanda/?tab=host[Datadog documentation^] and https://github.com/DataDog/integrations-extras/tree/master/redpanda[Redpanda Datadog integration^].
71
+
NOTE: Because the OpenMetrics endpoint in Redpanda Cloud aggregates Redpanda metrics for all cluster services, only a single Datadog agent is required. The agent must run in a container in your own container infrastructure. Redpanda does not support launching this container inside a Dedicated or BYOC Kubernetes cluster. For more information, see the https://docs.datadoghq.com/integrations/redpanda/?tab=host[Datadog documentation^] and https://github.com/DataDog/integrations-extras/tree/master/redpanda[Redpanda Datadog integration^].
0 commit comments