chore: fixes links

newrelic · May 3, 2024 · 4af5332 · 4af5332
1 parent 7e8fed3
commit 4af5332
Showing 1 changed file with 2 additions and 2 deletions.
diff --git a/src/content/docs/logs/forward-logs/kubernetes-plugin-log-forwarding.mdx b/src/content/docs/logs/forward-logs/kubernetes-plugin-log-forwarding.mdx
@@ -64,8 +64,8 @@ To configure your Kubernetes cluster to send the log forwarder internal metrics
 
 <Callout variant="tip">
   The `newrelic-logging` Helm chart uses [Fluent Bit](https://fluentbit.io/) together with New Relic's [newrelic-fluent-bit-output plugin]((https://github.com/newrelic/newrelic-fluent-bit-output)) to send logs to New Relic. The `fluentBit.sendMetrics` configuration option enables the collection of their individual metrics:
-  - **Fluent Bit internal metrics**: emitted by Fluent Bit in Prometheus format and delivered to New Relic's Prometheus Export endpoint. **These are the recommended ones to troubleshoot a Kubernetes cluster** because they can be faceted by `cluster_name`, `node_name` and `hostname` (pod name).
-  - **[newrelic-fluent-bit-output](https://github.com/newrelic/newrelic-fluent-bit-output)'s internal plugin metrics**: collected by the output plugin and sent to New Relic's Metric API. These metrics do not contain dimensions, so they cannot be narrowed down to a particular cluster or host. Despite this, it is useful to capture them for a single cluster to assess what is the overall latency when delivering the logs to the New Relic Logs API or to observe potential packaging problems.
+  - **[Fluent Bit internal metrics](https://docs.fluentbit.io/manual/administration/monitoring#for-v2-metrics)**: emitted by Fluent Bit in Prometheus format and delivered to New Relic's Prometheus Export endpoint. **These are the recommended ones to troubleshoot a Kubernetes cluster** because they can be faceted by `cluster_name`, `node_name` and `hostname` (pod name).
+  - **[newrelic-fluent-bit-output's internal plugin metrics](https://github.com/newrelic/newrelic-fluent-bit-output?tab=readme-ov-file#troubleshooting-metrics)**: collected by the output plugin and sent to New Relic's Metric API. These metrics do not contain dimensions, so they cannot be narrowed down to a particular cluster or host. Despite this, it is useful to capture them for a single cluster to assess what is the overall latency when delivering the logs to the New Relic Logs API or to observe potential packaging problems.
 </Callout>
 
 <Callout variant="tip">