fix(K8s): Updated the Explore your Kubernetes data category. #18085
Conversation
nbaenam
added
content
|
Hi @nbaenam 👋 Thanks for your pull request! Your PR is in a queue, and a writer will take a look soon. We generally publish small edits within one business day, and larger edits within three days. We will automatically generate a preview of your request, and will comment with a link when the preview is ready (usually 10 to 20 minutes). |
❌ Deploy Preview for docs-website-netlify failed. Why did it fail? →
|
There was a problem hiding this comment.
@nbaenam Thanks for making all of these changes! I added some comments. See what you think.
...ubernetes-pixie/kubernetes-integration/understand-use-data/find-use-your-kubernetes-data.mdx
Show resolved
Hide resolved
...ubernetes-pixie/kubernetes-integration/understand-use-data/find-use-your-kubernetes-data.mdx
Outdated
Show resolved
Hide resolved
.../kubernetes-pixie/kubernetes-integration/understand-use-data/kubernetes-cluster-explorer.mdx
Show resolved
Hide resolved
...ubernetes-pixie/kubernetes-integration/understand-use-data/kubernetes-events-integration.mdx
Outdated
Show resolved
Hide resolved
...ubernetes-pixie/kubernetes-integration/understand-use-data/kubernetes-events-integration.mdx
Outdated
Show resolved
Hide resolved
| </CollapserGroup> | ||
|
|
||
|
|
||
| Go here for [uninstallation instructions](/docs/kubernetes-pixie/kubernetes-integration/installation/uninstall-kubernetes/). | ||
|
|
||
| ## Troubleshoot your Kubernetes plugin for log forwarding installation [#troubleshoot-installation] |
There was a problem hiding this comment.
@nbaenam this section seems to cover both the Kubernetes log forwarding plugin and the Fluent Bit approach. If that's the case, do you need to broaden this heading to include both?
There was a problem hiding this comment.
I've removed some of the content here and added a link to [this document ](Fluent Bit plugin for log forwarding) that explains everything related to Fluent Bit. Let me know if this solution works for you.
src/content/docs/logs/forward-logs/kubernetes-plugin-log-forwarding.mdx
Outdated
Show resolved
Hide resolved
src/content/docs/logs/forward-logs/kubernetes-plugin-log-forwarding.mdx
Outdated
Show resolved
Hide resolved
|
|
||
| * **[`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 only contain the `cluster_name` dimension, so they can be narrowed down to a particular cluster but not to a particular host or pod. They're useful to assess the overall latency when delivering the logs to the New Relic Logs API or to observe potential packaging problems. | ||
|
|
||
| We capture Fluent Bit's internal metrics by using its [`prometheus_scrape` input plugin](https://docs.fluentbit.io/manual/pipeline/inputs/prometheus-scrape-metrics) in conjunction with its [`prometheus_remote_write` output plugin](https://docs.fluentbit.io/manual/pipeline/outputs/prometheus-remote-write). All the Prometheus `counter` metrics are actually cumulative counters, but we automatically perform a delta conversion when they are ingested at New Relic to ease querying them using NRQL later. You can find more details [here](/docs/data-apis/understand-data/metric-data/cumulative-metrics/). | ||
|
|
||
| ## View log data [#find-data] |
There was a problem hiding this comment.
@nbaenam maybe this should precede the troubleshooting section?
There was a problem hiding this comment.
I think this paragraph must be here because it refers to Fluent Bit's internal metrics. I've moved inside newrelic-fluent-bit-output's internal plugin metrics
src/content/docs/logs/forward-logs/kubernetes-plugin-log-forwarding.mdx
Outdated
Show resolved
Hide resolved
|
Replace with this one: 18374 |
Updated these docs:
Ticket: NR-266821