feat(ebpf ga): eBPF eAPM GA and eBPF Network Monitoring PP release docs #22047
Conversation
WriteMayur
added
content
|
Hi @WriteMayur 👋 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. Please ensure the propsed changes look good by building it first in your local environment. Refer to this contribution guide to get the site up and running in your local. If you really require a preview url, reach out to one of the writers and they will generate one for you. |
|
netlify build |
🚀 Netlify Preview Building!If the build is successful, the preview for this pull request will be available at the following URL (usually takes 10-20 minutes): |
|
netlify build |
|
netlify build |
src/content/docs/ebpf/overview.mdx
Outdated
|
|
||
| This approach allows you to: | ||
|
|
||
| * **Simplify Observability:** Use one agent to automatically discover and monitor all services, regardless of programming language. |
There was a problem hiding this comment.
@WriteMayur Can we add "works on Kubernetes and Linux host/containers"?
| ### If no eBPF data appears at all: | ||
|
|
||
| 1. **Check network connectivity**: Ensure that the OTLP (OpenTelemetry Protocol) endpoint is not blocked by any firewall or network configuration. Verify these URLs are accessible: | ||
| * `otlp.nr-data.net:4317` |
There was a problem hiding this comment.
@WriteMayur according to "eBPF Agent FAQ & Troubleshooting" doc, only 443 port
|
|
||
| 1. **Check network connectivity**: Ensure that the OTLP (OpenTelemetry Protocol) endpoint is not blocked by any firewall or network configuration. Verify these URLs are accessible: | ||
| * `otlp.nr-data.net:4317` | ||
| * `otlp.eu01.nr-data.net:4317` (EU region only) |
There was a problem hiding this comment.
@WriteMayur according to "eBPF Agent FAQ & Troubleshooting" doc, only 443 port
|
netlify build |
|
netlify build |
|
netlify build |
|
netlify build |
|
netlify build |
|
netlify build |
|
netlify build |
|
netlify build |
WriteMayur
changed the title
| * [eBPF network metrics](#ebpf-network-metrics) | ||
|
|
||
|
|
||
| ## Use cases [#use-cases] |
There was a problem hiding this comment.
These are not use cases. These are features of the offering. A use case would be an example of how this feature would be used in a scenario.
| This feature is currently provided as part of a preview pursuant to our [pre-release policies](/docs/licenses/license-information/referenced-policies/new-relic-pre-release-policy/). It is not available to customers subject to HIPAA or FedRAMP regulations. | ||
| </Callout> | ||
|
|
||
| The eBPF network metrics provides deep visibility into the network communication of your applications. It captures granular TCP, IP, and DNS telemetry directly from the kernel, solving a major source of application performance issues. This capability is complementary to APM (both eAPM and traditional APM) and works independently to give you a complete picture of your application's communication health, helping you definitively answer the question: "Is it the application or the network?" |
There was a problem hiding this comment.
How does it SOLVE the issue? It helps identify the issue....correct?
vpayyapilly
left a comment
vpayyapilly
left a comment
There was a problem hiding this comment.
@WriteMayur See my comments. Mostly minor. No show-stoppers.
This PR creates/udpates docs to prepare for following upcoming releases of eBPF monitoring: