Skip to content

Commit

Permalink
Sprint review edits
Browse files Browse the repository at this point in the history
  • Loading branch information
bradleycamacho committed Mar 21, 2024
1 parent 66ea1aa commit feae3b6
Showing 1 changed file with 52 additions and 56 deletions.
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,7 @@ freshnessValidatedDate: never
---
import envoyDashboard from 'images/infrastructure_screenshot_full-envoy-dashboard.webp'

Gain deep insights into MongoDB performance with seamless data integration into New Relic. Monitor key metrics to ensure the optimal performance of your Envoy clusters. Create alerts to stay ahead of spikes, build custom dashboards for tailored views, and proactively optimize your database monitoring.
Gain deep insights into Envoy performance with seamless data integration into New Relic. Monitor key metrics to ensure the optimal performance of your Envoy clusters. Create alerts to stay ahead of spikes, build custom dashboards for tailored views, and proactively optimize your database monitoring.

<img
title="Envoy dashboard"
Expand All @@ -33,62 +33,58 @@ To use the Envoy integration, you need to also [install the infrastructure agent
To set up the Envoy integration, follow these steps:

1. Create a file named `nri-prometheus-config.yml` in this path:
```shell
cd /etc/newrelic-infra/integrations.d
```

```shell
cd /etc/newrelic-infra/integrations.d
```
2. Add the following snippet to your `nri-prometheus-config.yml` file to enable the agent to capture Envoy data:

```yml
integrations:
- name: nri-prometheus
config:
# When standalone is set to false nri-prometheus requires an infrastructure agent to work and send data. Defaults to true
standalone: false

# When running with infrastructure agent emitters will have to include infra-sdk
emitters: infra-sdk

# The name of your cluster. It's important to match other New Relic products to relate the data.
cluster_name: "YOUR_DESIRED_CLUSTER_NAME"

targets:
- description: Envoy metrics list
urls: ["http://<ip-address>:9901/stats/prometheus"]

# tls_config:
# ca_file_path: "/etc/etcd/etcd-client-ca.crt"
# cert_file_path: "/etc/etcd/etcd-client.crt"
# key_file_path: "/etc/etcd/etcd-client.key"

# Whether the integration should run in verbose mode or not. Defaults to false
verbose: false

# Whether the integration should run in audit mode or not. Defaults to false.
# Audit mode logs the uncompressed data sent to New Relic. Use this to log all data sent.
# It does not include verbose mode. This can lead to a high log volume, use with care
audit: false

# The HTTP client timeout when fetching data from endpoints. Defaults to 30s.
# scrape_timeout: "30s"

# Length in time to distribute the scraping from the endpoints
scrape_duration: "5s"

# Number of worker threads used for scraping targets.
# For large clusters with many (&gt;400) endpoints, slowly increase until scrape
# time falls between the desired `scrape_duration`.
# Increasing this value too much will result in huge memory consumption if too
# many metrics are being scraped.
# Default: 4
# worker_threads: 4

# Whether the integration should skip TLS verification or not. Defaults to false
insecure_skip_verify: true
timeout: 10s
```


```yml
integrations:
- name: nri-prometheus
config:
# When standalone is set to false nri-prometheus requires an infrastructure agent to work and send data. Defaults to true
standalone: false

# When running with infrastructure agent emitters will have to include infra-sdk
emitters: infra-sdk

# The name of your cluster. It's important to match other New Relic products to relate the data.
cluster_name: "YOUR_DESIRED_CLUSTER_NAME"

targets:
- description: Envoy metrics list
urls: ["http://<ip-address>:9901/stats/prometheus"]

# tls_config:
# ca_file_path: "/etc/etcd/etcd-client-ca.crt"
# cert_file_path: "/etc/etcd/etcd-client.crt"
# key_file_path: "/etc/etcd/etcd-client.key"

# Whether the integration should run in verbose mode or not. Defaults to false
verbose: false

# Whether the integration should run in audit mode or not. Defaults to false.
# Audit mode logs the uncompressed data sent to New Relic. Use this to log all data sent.
# It does not include verbose mode. This can lead to a high log volume, use with care
audit: false

# The HTTP client timeout when fetching data from endpoints. Defaults to 30s.
# scrape_timeout: "30s"

# Length in time to distribute the scraping from the endpoints
scrape_duration: "5s"

# Number of worker threads used for scraping targets.
# For large clusters with many (&gt;400) endpoints, slowly increase until scrape
# time falls between the desired `scrape_duration`.
# Increasing this value too much will result in huge memory consumption if too
# many metrics are being scraped.
# Default: 4
# worker_threads: 4

# Whether the integration should skip TLS verification or not. Defaults to false
insecure_skip_verify: true
timeout: 10s
```
</Step>
<Step>

Expand Down

0 comments on commit feae3b6

Please sign in to comment.