-
Notifications
You must be signed in to change notification settings - Fork 234
otel apps to support remote flow #6292
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
base: main
Are you sure you want to change the base?
Conversation
docs/integrations/web-servers/opentelemetry/apache-opentelemetry.md
Outdated
Show resolved
Hide resolved
docs/integrations/web-servers/opentelemetry/apache-opentelemetry.md
Outdated
Show resolved
Hide resolved
…ry.md Co-authored-by: Alekh Nema <[email protected]>
Co-authored-by: Alekh Nema <[email protected]>
…/SumoLogic/sumologic-documentation into Otel-Apps-to-support-remote-flow
…/SumoLogic/sumologic-documentation into Otel-Apps-to-support-remote-flow
| @@ -0,0 +1,8 @@ | |||
| In this step, you will configure the yaml required for Docker Collection. Below are the inputs required for configuration: | |||
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.
| In this step, you will configure the yaml required for Docker Collection. Below are the inputs required for configuration: | |
| In this step, you will configure the YAML required for Docker Collection. Below are the inputs required for configuration: |
| @@ -0,0 +1,9 @@ | |||
| In this step, you will configure the yaml required for Elasticsearch collection. Below are the inputs required for configuration: | |||
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.
| In this step, you will configure the yaml required for Elasticsearch collection. Below are the inputs required for configuration: | |
| In this step, you will configure the YAML required for Elasticsearch collection. Below are the inputs required for configuration: |
| @@ -0,0 +1,20 @@ | |||
| In this step, you will configure the yaml required for Linux Collection. Below are the inputs required for configuration: | |||
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.
| In this step, you will configure the yaml required for Linux Collection. Below are the inputs required for configuration: | |
| In this step, you will configure the YAML required for Linux Collection. Below are the inputs required for configuration: |
| @@ -0,0 +1,20 @@ | |||
| In this step, you will configure the yaml required for Mac Collection. Below are the inputs required for configuration: | |||
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.
| In this step, you will configure the yaml required for Mac Collection. Below are the inputs required for configuration: | |
| In this step, you will configure the YAML required for Mac Collection. Below are the inputs required for configuration: |
| @@ -0,0 +1,10 @@ | |||
| In this step, you will configure the yaml required for MySQL collection. Below are the inputs required for configuration: | |||
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.
| In this step, you will configure the yaml required for MySQL collection. Below are the inputs required for configuration: | |
| In this step, you will configure the YAML required for MySQL collection. Below are the inputs required for configuration: |
| @@ -0,0 +1,8 @@ | |||
| In this step, you will configure the yaml required for Nginx collection. Below are the inputs required for configuration: | |||
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.
| In this step, you will configure the yaml required for Nginx collection. Below are the inputs required for configuration: | |
| In this step, you will configure the YAML required for Nginx collection. Below are the inputs required for configuration: |
| @@ -0,0 +1,12 @@ | |||
| In this step, you will configure the yaml required for PostgreSQL collection. Below are the inputs required for configuration: | |||
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.
| In this step, you will configure the yaml required for PostgreSQL collection. Below are the inputs required for configuration: | |
| In this step, you will configure the YAML required for PostgreSQL collection. Below are the inputs required for configuration: |
| @@ -0,0 +1,13 @@ | |||
| In this step, you will configure the yaml required for Local File Collection. Below are the inputs required for configuration: | |||
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.
| In this step, you will configure the yaml required for Local File Collection. Below are the inputs required for configuration: | |
| In this step, you will configure the YAML required for Local File Collection. Below are the inputs required for configuration: |
| <TimestampParsing/> | ||
|
|
||
| <PuppetEnv/> | ||
| **Processing Rules**. You can add **processing rules** for logs/metrics collected. To learn more, refer to [Processing Rules](/docs/send-data/opentelemetry-collector/remote-management/processing-rules). |
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.
@amee-sumo, it looks a little strange to have Timestamp Parsing and Processing Rules not in the bulleted list. But it's oaky. I think you can leave it like that.
But you may want to make the Processing Rules item a reuse file.
| :::note | ||
| If you want to configure your source locally, you can do so by downloading the YAML file. For details, see [Configure OpenTelemetry collectors locally](/docs/integrations/sumo-apps/opentelemetry-collector-insights/#configure-opentelemetry-collectors-locally). | ||
| ::: |
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.
@amee-sumo, you should probably add this note to the end of the reuse file otel-collector-installation.md, since you add it every time after you call that file:
:::note
If you want to configure your source locally, you can do so by downloading the YAML file. For details, see Configure OpenTelemetry collectors locally.
:::
jpipkin1
left a comment
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.
@amee-sumo, great work! I have a few minor suggestions. I'll take another look at the PR after you've addressed the suggestions.
Purpose of this pull request
This pull request...
Select the type of change
Ticket (if applicable)
https://sumologic.atlassian.net/browse/SUMO-278252