-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Add new supported OTel integrations #28253
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,38 @@ | ||
--- | ||
title: Apache Web Server Metrics | ||
further_reading: | ||
- link: "/opentelemetry/collector_exporter/" | ||
tag: "Documentation" | ||
text: "Setting Up the OpenTelemetry Collector" | ||
--- | ||
|
||
## Overview | ||
|
||
{{< img src="/opentelemetry/collector_exporter/apache_metrics.png" alt="OpenTelemetry Apache metrics in an Apache dashboard" style="width:100%;" >}} | ||
|
||
The [Apache receiver][1] allows for collection of Apache Web Server metrics. Configure the receiver according to the specifications of the latest version of the `apachereceiver`. | ||
|
||
For more information, see the OpenTelemetry project documentation for the [Apache receiver][1]. | ||
|
||
## Setup | ||
|
||
To collect Apache Web Server metrics with OpenTelemetry for use with Datadog: | ||
|
||
1. Configure the [Apache receiver][1] in your OpenTelemetry Collector configuration. | ||
2. Ensure the OpenTelemetry Collector is [configured to export to Datadog][4]. | ||
|
||
See the [Apache receiver documentation][1] for detailed configuration options and requirements. | ||
|
||
## Data collected | ||
|
||
{{< mapping-table resource="apache.csv">}} | ||
|
||
See [OpenTelemetry Metrics Mapping][2] for more information. | ||
|
||
## Further reading | ||
|
||
{{< partial name="whats-next/whats-next.html" >}} | ||
|
||
[1]: https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/receiver/apachereceiver | ||
[2]: /opentelemetry/guide/metrics_mapping/ | ||
[4]: /opentelemetry/setup/collector_exporter/ |
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,39 @@ | ||
--- | ||
title: HAProxy Metrics | ||
further_reading: | ||
- link: "/opentelemetry/collector_exporter/" | ||
tag: "Documentation" | ||
text: "Setting Up the OpenTelemetry Collector" | ||
--- | ||
|
||
## Overview | ||
|
||
{{< img src="/opentelemetry/collector_exporter/haproxy_metrics.png" alt="OpenTelemetry HAProxy metrics in an HAProxy dashboard" style="width:100%;" >}} | ||
|
||
The [HAProxy receiver][1] allows for collection of HAProxy metrics and access to the [HAProxy Overview][4] dashboard. Configure the receiver according to the specifications of the latest version of the `haproxyreceiver`. | ||
|
||
For more information, see the OpenTelemetry project documentation for the [HAProxy receiver][1]. | ||
|
||
## Setup | ||
|
||
To collect HAProxy metrics with OpenTelemetry for use with Datadog: | ||
|
||
1. Configure the [HAProxy receiver][1] in your OpenTelemetry Collector configuration. | ||
2. Ensure the OpenTelemetry Collector is [configured to export to Datadog][5]. | ||
|
||
See the [HAProxy receiver documentation][1] for detailed configuration options and requirements. | ||
|
||
## Data collected | ||
|
||
{{< mapping-table resource="haproxy.csv">}} | ||
|
||
See [OpenTelemetry Metrics Mapping][2] for more information. | ||
|
||
## Further reading | ||
|
||
{{< partial name="whats-next/whats-next.html" >}} | ||
|
||
[1]: https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/receiver/haproxyreceiver | ||
[2]: /opentelemetry/guide/metrics_mapping/ | ||
[4]: https://app.datadoghq.com/dash/integration/28/haproxy---overview | ||
[5]: /opentelemetry/setup/collector_exporter/ |
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,39 @@ | ||
--- | ||
title: IIS Metrics | ||
further_reading: | ||
- link: "/opentelemetry/collector_exporter/" | ||
tag: "Documentation" | ||
text: "Setting Up the OpenTelemetry Collector" | ||
--- | ||
|
||
## Overview | ||
|
||
{{< img src="/opentelemetry/collector_exporter/iis_metrics.png" alt="OpenTelemetry IIS metrics in an IIS dashboard" style="width:100%;" >}} | ||
|
||
The [IIS receiver][1] allows for collection of IIS (Internet Information Services) metrics and access to the [IIS Overview][4] dashboard. Configure the receiver according to the specifications of the latest version of the `iisreceiver`. | ||
|
||
For more information, see the OpenTelemetry project documentation for the [IIS receiver][1]. | ||
|
||
## Setup | ||
|
||
To collect IIS metrics with OpenTelemetry for use with Datadog: | ||
|
||
1. Configure the [IIS receiver][1] in your OpenTelemetry Collector configuration. | ||
2. Ensure the OpenTelemetry Collector is [configured to export to Datadog][5]. | ||
|
||
See the [IIS receiver documentation][1] for detailed configuration options and requirements. | ||
|
||
## Data collected | ||
|
||
{{< mapping-table resource="iis.csv">}} | ||
|
||
See [OpenTelemetry Metrics Mapping][2] for more information. | ||
|
||
## Further reading | ||
|
||
{{< partial name="whats-next/whats-next.html" >}} | ||
|
||
[1]: https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/receiver/iisreceiver | ||
[2]: /opentelemetry/guide/metrics_mapping/ | ||
[4]: https://app.datadoghq.com/screen/integration/243/iis---overview | ||
[5]: /opentelemetry/setup/collector_exporter/ |
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -17,7 +17,7 @@ OTel Kafka Metrics Remapping is in public alpha. It is available in versions >= | |
|
||
The [Kafka metrics receiver][1], [JMX Receiver][2]/ [JMX Metrics Gatherer][3] allow collecting Kafka metrics and access to the out of the box [Kafka Dashboard][7], "Kafka, Zookeeper and Kafka Consumer Overview". | ||
|
||
Please note that the [JMX Receiver][2] and [JMX Metrics Gatherer][3] should be considered as replacements. They collect the same set of metrics ([JMX Receiver][2] launches the [JMX Metrics Gatherer][3]). | ||
**Note**: the [JMX Receiver][2] and [JMX Metrics Gatherer][3] should be considered as replacements. They collect the same set of metrics ([JMX Receiver][2] launches the [JMX Metrics Gatherer][3]). | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I'm having some trouble understanding the landscape of the Kafka metrics receiver, JMX Receiver, and JMX Metrics Gatherer. I can sort of guess that JMX Receiver and JMX Metrics Gatherer are always used together, and this pair is an alternative to the Kafka metrics receiver—is that true? When would you use one over the other? As-is, this first sentence could be interpreted to mean that the JMX Receiver and JMX Metrics Gatherer are replacements for each other, which seems misleading. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Good point! I will update this in a follow-up PR. |
||
|
||
|
||
## Kafka metrics receiver | ||
|
@@ -103,7 +103,7 @@ The JMX Receiver has the following requirements: | |
- JRE is available on the host in which you are running the collector. | ||
- The JMX Metric Gatherer JAR is available on the host in which you are running the collector. You can download the most recent release of the JMX Metric Gatherer JAR [here][1]. | ||
|
||
Because the OTel collector default image does not meet the requirements above, a custom image needs to be built. Please refer to the Dockerfile below for an example image that contains the collector binary, JRE, and JMX Metrics Gatherer Jar. | ||
Because the OTel collector default image does not meet the requirements above, a custom image needs to be built. See the Dockerfile below for an example image that contains the collector binary, JRE, and JMX Metrics Gatherer Jar. | ||
|
||
Dockerfile: | ||
```Dockerfile | ||
|
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,39 @@ | ||
--- | ||
title: MySQL Metrics | ||
further_reading: | ||
- link: "/opentelemetry/collector_exporter/" | ||
tag: "Documentation" | ||
text: "Setting Up the OpenTelemetry Collector" | ||
--- | ||
|
||
## Overview | ||
|
||
{{< img src="/opentelemetry/collector_exporter/mysql_metrics.png" alt="OpenTelemetry MySQL metrics in a MySQL dashboard" style="width:100%;" >}} | ||
|
||
The [MySQL receiver][1] allows for collection of MySQL metrics and access to the [MySQL Overview][4] dashboard. Configure the receiver according to the specifications of the latest version of the `mysqlreceiver`. | ||
|
||
For more information, see the OpenTelemetry project documentation for the [MySQL receiver][1]. | ||
|
||
## Setup | ||
|
||
To collect MySQL metrics with OpenTelemetry for use with Datadog: | ||
|
||
1. Configure the [MySQL receiver][1] in your OpenTelemetry Collector configuration. | ||
2. Ensure the OpenTelemetry Collector is [configured to export to Datadog][5]. | ||
|
||
See the [MySQL receiver documentation][1] for detailed configuration options and requirements. | ||
|
||
## Data collected | ||
|
||
{{< mapping-table resource="mysql.csv">}} | ||
|
||
See [OpenTelemetry Metrics Mapping][2] for more information. | ||
|
||
## Further reading | ||
|
||
{{< partial name="whats-next/whats-next.html" >}} | ||
|
||
[1]: https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/receiver/mysqlreceiver | ||
[2]: /opentelemetry/guide/metrics_mapping/ | ||
[4]: https://app.datadoghq.com/dash/integration/12/mysql---overview | ||
[5]: /opentelemetry/setup/collector_exporter/ |
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,39 @@ | ||
--- | ||
title: NGINX Metrics | ||
further_reading: | ||
- link: "/opentelemetry/collector_exporter/" | ||
tag: "Documentation" | ||
text: "Setting Up the OpenTelemetry Collector" | ||
--- | ||
|
||
## Overview | ||
|
||
{{< img src="/opentelemetry/collector_exporter/nginx_metrics.png" alt="OpenTelemetry NGINX metrics in a NGINX dashboard" style="width:100%;" >}} | ||
|
||
The [NGINX receiver][1] allows for collection of NGINX metrics and access to the [NGINX Overview][4] dashboard. Configure the receiver according to the specifications of the latest version of the `nginxreceiver`. | ||
|
||
For more information, see the OpenTelemetry project documentation for the [NGINX receiver][1]. | ||
|
||
## Setup | ||
|
||
To collect NGINX metrics with OpenTelemetry for use with Datadog: | ||
|
||
1. Configure the [NGINX receiver][1] in your OpenTelemetry Collector configuration. | ||
2. Ensure the OpenTelemetry Collector is [configured to export to Datadog][5]. | ||
|
||
See the [NGINX receiver documentation][1] for detailed configuration options and requirements. | ||
|
||
## Data collected | ||
|
||
{{< mapping-table resource="nginx.csv">}} | ||
|
||
See [OpenTelemetry Metrics Mapping][2] for more information. | ||
|
||
## Further reading | ||
|
||
{{< partial name="whats-next/whats-next.html" >}} | ||
|
||
[1]: https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/receiver/nginxreceiver | ||
[2]: /opentelemetry/guide/metrics_mapping/ | ||
[4]: https://app.datadoghq.com/dash/integration/21/nginx---overview | ||
[5]: /opentelemetry/setup/collector_exporter/ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These menu items aren't showing up in the staging preview. Is it because the weights are off? (they're 8101/8102/8103 while the siblings are 810, 811)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Weird! I see them?

There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
oh! my bad, I didn't realize they were nested like that. ignore my comment!!