Skip to content

Conversation

@amee-sumo
Copy link
Collaborator

@amee-sumo amee-sumo commented Feb 10, 2026

Purpose of this pull request

This pull request...

Select the type of change

  • Minor Changes - Typos, formatting, slight revisions
  • Update Content - Revisions, updating sections
  • New Content - New features, sections, pages, tutorials
  • Site and Tools - .clabot, version updates, maintenance, dependencies, new packages for the site (Docusaurus, Gatsby, React, etc.)

Ticket (if applicable)

https://sumologic.atlassian.net/browse/SUMO-278252

@amee-sumo amee-sumo self-assigned this Feb 10, 2026
@amee-sumo amee-sumo requested a review from kimsauce as a code owner February 10, 2026 09:53
@amee-sumo amee-sumo added the doc:update Revisions and updates to content label Feb 10, 2026
@amee-sumo amee-sumo added the do-not-merge Pull requests that should not be merged label Feb 10, 2026
@amee-sumo amee-sumo requested review from a team and mafsumo as code owners February 10, 2026 09:53
@cla-bot cla-bot bot added the cla-signed Contributor approved, listed in .clabot file label Feb 10, 2026
@amee-sumo amee-sumo marked this pull request as draft February 10, 2026 09:53
@amee-sumo amee-sumo marked this pull request as ready for review February 11, 2026 16:49
@amee-sumo amee-sumo requested a review from a team as a code owner February 11, 2026 16:49
@amee-sumo amee-sumo requested a review from sumoanema February 11, 2026 17:21
@@ -0,0 +1,8 @@
In this step, you will configure the yaml required for Docker Collection. Below are the inputs required for configuration:
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
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:
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
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:
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
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:
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
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:
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
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:
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
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:
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
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:
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
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:

Comment on lines +76 to +78
<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).
Copy link
Collaborator

@jpipkin1 jpipkin1 Feb 11, 2026

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.

Comment on lines +64 to +66
:::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).
:::
Copy link
Collaborator

@jpipkin1 jpipkin1 Feb 11, 2026

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.
:::

Copy link
Collaborator

@jpipkin1 jpipkin1 left a 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

cla-signed Contributor approved, listed in .clabot file do-not-merge Pull requests that should not be merged doc:update Revisions and updates to content

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants