SUMO-251067 | Apoorv | Add. PR review comments

Apoorvkudesia-sumologic · Apoorvkudesia-sumologic · commit 65d5b38cc6bd · 2025-02-03T19:23:57.000+05:30
diff --git a/docs/integrations/app-development/bitbucket.md b/docs/integrations/app-development/bitbucket.md
@@ -125,7 +125,6 @@ In this step, you configure a Hosted Collector to receive Webhook Events from Bi
 8. **Triggers** - Click on Choose from a full list of triggers, and choose all triggers under Repository, Issue and Pull Request.
 9. Click **Save**
 
-
 ### Step 3: Configure the Bitbucket CI/CD Pipeline to Collect Deploy Events
 
 A Bitbucket pipe needs to be configured to send code deploy status to Sumo Logic. Add the following pipe code to the step section of your deployment part of the `bitbucket-pipelines.yml` file. Replace `SUMOLOGIC_HTTP_URL` with HTTP Source URL configured in Step 1.
@@ -141,12 +140,9 @@ If you want to deployment events to multiple Sumo Logic orgs, include a `-pipe`
 
 For reference: This is how the [bitbucket-pipelines.yml](https://bitbucket.org/app-dev-sumo/backendservice/src/master/bitbucket-pipelines.yml) looks after adding deploy pipe code to our sample Bitbucket CI/CD pipeline.
 
-
 ### Step 4: Enable Bitbucket Event-Key tagging at Sumo Logic
 
-Sumo Logic needs to understand the event type for incoming events (for example, repo:push events). To enable this, the [X-Event-Key](https://confluence.atlassian.com/bitbucket/event-payloads-740262817.html#EventPayloads-HTTPheaders) event type is automatically added to the [Fields](/docs/manage/fields) during installation of the app.
-
-
+To properly identify the event type for incoming events (for example, repo:push events), Sumo Logic automatically adds the [X-Event-Key](https://confluence.atlassian.com/bitbucket/event-payloads-740262817.html#EventPayloads-HTTPheaders) event type to the [Fields](/docs/manage/fields) during app installation.
 
 ## Installing the Bitbucket App
 
diff --git a/docs/integrations/app-development/github.md b/docs/integrations/app-development/github.md
@@ -158,8 +158,7 @@ To configure a GitHub Webhook:
 
 ### Enable GitHub Event tagging at Sumo Logic
 
-Sumo Logic needs to understand the event type for incoming events. To enable this, the [x-github-event](https://docs.github.com/en/developers/webhooks-and-events/webhook-events-and-payloads) event type is automatically added to the [Fields](/docs/manage/fields) during installation of the app.
-
+To properly identify the event type for incoming events, Sumo Logic automatically adds the [x-github-event](https://docs.github.com/en/developers/webhooks-and-events/webhook-events-and-payloads) event type to the [Fields](/docs/manage/fields) during app installation.
 
 ## Installing the GitHub App
 
diff --git a/docs/integrations/app-development/gitlab.md b/docs/integrations/app-development/gitlab.md
@@ -93,9 +93,7 @@ Refer to the [GitLab Webhooks documentation](https://docs.gitlab.com/ee/user/pro
 
 ### Step 3: Enable GitLab Event tagging at Sumo Logic
 
-Sumo Logic needs to understand the event type for incoming events. To enable this, the [x-gitlab-event](https://docs.gitlab.com/ee/user/project/integrations/webhook_events.html#push-events) event type is automatically added to the [Fields](/docs/manage/fields) during installation of the app.
-
-
+To properly identify the event type for incoming events, Sumo Logic automatically adds the [x-gitlab-event](https://docs.gitlab.com/ee/user/project/integrations/webhook_events.html#push-events) event type to the [Fields](/docs/manage/fields) during app installation.
 
 ## Installing the GitLab App
 
diff --git a/docs/integrations/containers-orchestration/activemq.md b/docs/integrations/containers-orchestration/activemq.md
@@ -51,25 +51,23 @@ Host: broker-3-activemq Name: /opt/activemq/data/activemq.log Category:logfile
 This App has been tested with following ActiveMQ versions:
 * 5.16.2.
 
-Configuring log and metric collection for the ActiveMQ App includes the following tasks:
+### Step 1: Configure fields in Sumo Logic
 
-### Step 1: Fields in Sumo Logic
+Configuring log and metric collection for the ActiveMQ App includes the following tasks:
 
 The following [fields](/docs/manage/fields/) will always be created automatically as a part of the app installation process:
-
-* `pod_labels_component`
-* `pod_labels_environment`
-* `pod_labels_messaging_system`
-* `pod_labels_messaging_cluster`
-
-
-If you're using ActiveMQ in a non-Kubernetes environment, these additional fields will get created automatically as a part of app installation process:
 * `component`
 * `environment`
 * `messaging_system`
 * `messaging_cluster`
 * `pod`
 
+If you're using ActiveMQ in a Kubernetes environment, the following additional fields will be automatically created as a part of the app installation process:
+* `pod_labels_component`
+* `pod_labels_environment`
+* `pod_labels_messaging_system`
+* `pod_labels_messaging_cluster`
+
 For information on setting up fields, see [Fields](/docs/manage/fields).
 
 
@@ -250,7 +248,7 @@ This section explains the steps to collect ActiveMQ logs from a Kubernetes envir
     annotations:
           tailing-sidecar: sidecarconfig;data:/opt/activemq/data/activemq.log
     ```
-   1. Make sure that the ActiveMQ pods are running and annotations are applied by using the command:
+   1. Ensure that the ActiveMQ pods are running and annotations are applied by using the command:
     ```bash
     kubectl describe pod <ActiveMQ_pod_name>
     ```
@@ -427,7 +425,7 @@ At this point, ActiveMQ logs should start flowing into Sumo Logic.
 import CreateMonitors from '../../reuse/apps/create-monitors.md';
 
 <CreateMonitors/>
-There are limits to how many alerts can be enabled
+There are limits to how many alerts can be enabled.
 
 :::note permissions required
 To install these monitors, you need to have the [Manage Monitors role capability](/docs/manage/users-roles/roles/role-capabilities/#alerting).
diff --git a/docs/integrations/containers-orchestration/kafka.md b/docs/integrations/containers-orchestration/kafka.md
@@ -67,23 +67,21 @@ messaging_cluster=* messaging_system="kafka" \
 
 This section provides instructions for configuring log and metric collection for the Sumo Logic App for Kafka.
 
-### Fields in Sumo Logic
+### Step 1: Configure fields in Sumo Logic
 
-The following [fields](https://help.sumologic.com/docs/manage/fields/) will always be created automatically as a part of the app installation process:
-
-* `pod_labels_component`
-* `pod_labels_environment`
-* `pod_labels_messaging_system`
-* `pod_labels_messaging_cluster`
-
-
-If you're using Kafka in a non-Kubernetes environment, these additional fields will get created automatically as a part of the app installation process:
+The following [fields](/docs/manage/fields/) will always be created automatically as a part of the app installation process:
 * `component`
 * `environment`
 * `messaging_system`
 * `messaging_cluster`
 * `pod`
 
+If you're using Kafka in a Kubernetes environment, the following additional fields will be automatically created as a part of the app installation process:
+* `pod_labels_component`
+* `pod_labels_environment`
+* `pod_labels_messaging_system`
+* `pod_labels_messaging_cluster`
+
 For information on setting up fields, see [Fields](/docs/manage/fields).
 
 ### Configure Collection for Kafka
@@ -216,7 +214,7 @@ This section explains the steps to collect Kafka logs from a Kubernetes environm
     kubectl describe pod <Kafka_pod_name>
     ```
    5. Sumo Logic Kubernetes collection will automatically start collecting logs from the pods having the annotations defined above.
-3. **FER to normalize the fields in Kubernetes environments**. Labels created in Kubernetes environments automatically are prefixed with `pod_labels`. To normalize these for our app to work, a Field Extraction Rule is automatically created named **AppObservabilityMessagingKafkaFER**
+3. **FER to normalize the fields in Kubernetes environments**. Labels created in Kubernetes environments automatically are prefixed with `pod_labels`. To normalize these for our app to work, a Field Extraction Rule named **AppObservabilityMessagingKafkaFER** is automatically created.
 
 </TabItem>
 <TabItem value="non-k8s">
diff --git a/docs/integrations/containers-orchestration/rabbitmq.md b/docs/integrations/containers-orchestration/rabbitmq.md
@@ -50,24 +50,22 @@ Host: broker-1 Name: /var/log/rabbitmq/rabbit.log Category: logfile
 
 This section provides instructions for configuring log and metric collection for the Sumo Logic App for RabbitMQ.
 
+### Step 1: Configure fields in Sumo Logic
 
-### Step 1: Fields in Sumo Logic
-
-The following [fields](https://help.sumologic.com/docs/manage/fields/) will always be created automatically as a part of the app installation process:
-
-* `pod_labels_component`
-* `pod_labels_environment`
-* `pod_labels_messaging_system`
-* `pod_labels_messaging_cluster`
-
-If you're using RabbitMQ in a non-Kubernetes environment, these additional fields will get created automatically as a part of the app installation process:
+The following [fields](/docs/manage/fields/) will always be created automatically as a part of the app installation process:
 * `component`
 * `environment`
 * `messaging_system`
 * `messaging_cluster`
 * `pod`
 
-For information on setting up fields, see [Sumo Logic Fields](/docs/manage/fields).
+If you're using RabbitMQ in a Kubernetes environment, the following additional fields will be automatically created as a part of the app installation process:
+* `pod_labels_component`
+* `pod_labels_environment`
+* `pod_labels_messaging_system`
+* `pod_labels_messaging_cluster`
+
+For information on setting up fields, see [Fields](/docs/manage/fields).
 
 ### Step 2: Configure Collection for RabbitMQ
 
@@ -195,7 +193,7 @@ For all other parameters see [this doc](/docs/send-data/collect-from-other-data-
 kubectl describe pod <RabbitMQ_pod_name>
 ```
    5. Sumo Logic Kubernetes collection will automatically start collecting logs from the pods having the annotations defined above.
-3. **FER to normalize the fields in Kubernetes environments**. Labels created in Kubernetes environments automatically are prefixed with `pod_labels`. To normalize these for our app to work, a Field Extraction Rule is automatically created named **AppObservabilityMessagingRabbitMQFER**
+3. **FER to normalize the fields in Kubernetes environments**. Labels created in Kubernetes environments automatically are prefixed with `pod_labels`. To normalize these for our app to work, a Field Extraction Rule named **AppObservabilityMessagingRabbitMQFER** is automatically created.
 
 </TabItem>
 <TabItem value="non-k8s">
