-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
fix(OTEL): audit of OTEL docs #18627
Conversation
Hi @ally-sassman 👋 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 ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
Warning
To change the Ruby agent configuration file, please submit an issue or open a PR in the |
Warning
To change the Ruby agent configuration file, please submit an issue or open a PR in the |
...erless-function-monitoring/aws-lambda-monitoring/opentelemetry/lambda-opentelemetry-java.mdx
Outdated
Show resolved
Hide resolved
Warning
To change the Ruby agent configuration file, please submit an issue or open a PR in the |
Warning
To change the Ruby agent configuration file, please submit an issue or open a PR in the |
Warning
To change the Ruby agent configuration file, please submit an issue or open a PR in the |
src/content/docs/apm/agents/ruby-agent/configuration/ruby-agent-configuration.mdx
Outdated
Show resolved
Hide resolved
…t-configuration.mdx
…bsite into OTEL-doc-review
…itoring/opentelemetry/lambda-opentelemetry-java.mdx
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.
Great job!! I added some suggestions! Take them or leave them ;-)
src/content/docs/opentelemetry/best-practices/opentelemetry-data-overview.mdx
Outdated
Show resolved
Hide resolved
src/content/docs/kubernetes-pixie/kubernetes-integration/installation/k8s-otel.mdx
Outdated
Show resolved
Hide resolved
src/content/docs/opentelemetry/best-practices/opentelemetry-best-practices-metrics.mdx
Outdated
Show resolved
Hide resolved
src/content/docs/opentelemetry/best-practices/opentelemetry-best-practices-resources.mdx
Outdated
Show resolved
Hide resolved
src/content/docs/opentelemetry/best-practices/opentelemetry-manage-data-ingest-volume.mdx
Outdated
Show resolved
Hide resolved
@@ -17,7 +17,7 @@ translationType: machine | |||
width="40%" | |||
style={{align: "left"}} | |||
title="Diagram of OTLP with collector" |
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.
title="Diagram of OTLP with collector"
@@ -17,7 +17,7 @@ Aqui está um exemplo do coletor como gateway, mas você também pode configurar | |||
width="40%" | |||
style={{align: "left"}} | |||
title="Diagram of OTLP with collector" |
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.
title="Diagram of OTLP with collector"
@@ -238,9 +238,9 @@ Follow these steps to configure and deploy the OpenTelemetry collector as an age | |||
<Step> | |||
### Configure the Kubernetes Attributes processor (discovery filter) [#discovery-filter] | |||
|
|||
When running the collector as an agent, you should apply a discovery filter so that the processor only discovers pods from the same host that it is running on. If you don't use a filter, resource usage can be unnecessarily high, especially on very large clusters. Once the filter is applied, each processor will only query the Kubernetes API for pods running on its own node. | |||
When running the Collector as an agent, you should apply a discovery filter so that the processor only discovers pods from the same host that it is running on. If you don't use a filter, resource usage can be unnecessarily high, especially on very large clusters. Once the filter is applied, each processor will only query the Kubernetes API for pods running on its own node. |
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.
I would write this:
the same host that it's running on.
src/content/docs/apm/apm-ui-pages/monitoring/external-services/external-services-setup.mdx
Outdated
Show resolved
Hide resolved
src/content/docs/apm/apm-ui-pages/monitoring/external-services/external-services-setup.mdx
Outdated
Show resolved
Hide resolved
src/content/docs/infrastructure/other-infrastructure-integrations/monitoring-airflow-ot.mdx
Outdated
Show resolved
Hide resolved
src/content/docs/kubernetes-pixie/kubernetes-integration/installation/k8s-otel.mdx
Outdated
Show resolved
Hide resolved
src/content/docs/kubernetes-pixie/kubernetes-integration/installation/k8s-otel.mdx
Outdated
Show resolved
Hide resolved
src/content/docs/kubernetes-pixie/kubernetes-integration/installation/k8s-otel.mdx
Outdated
Show resolved
Hide resolved
.../opentelemetry/get-started/collector-processing/opentelemetry-collector-processing-intro.mdx
Outdated
Show resolved
Hide resolved
.../opentelemetry/get-started/collector-processing/opentelemetry-collector-processing-intro.mdx
Outdated
Show resolved
Hide resolved
.../opentelemetry/get-started/collector-processing/opentelemetry-collector-processing-intro.mdx
Outdated
Show resolved
Hide resolved
.../opentelemetry/get-started/collector-processing/opentelemetry-collector-processing-intro.mdx
Outdated
Show resolved
Hide resolved
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.
Super great work!!
This PR covers an extensive review of the OTEL docs: