Skip to content

Commit 05f02c2

Browse files
reverting application-components
1 parent 1a3fc31 commit 05f02c2

File tree

1 file changed

+3
-5
lines changed

1 file changed

+3
-5
lines changed

docs/observability/application-components.md

Lines changed: 3 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -223,9 +223,9 @@ Refer to the documentation for the app you're using. App Components Solution cur
223223
* [Oracle](/docs/integrations/databases/oracle)
224224

225225

226-
### Configure fields in Sumo Logic
226+
### Configure Fields in Sumo Logic
227227

228-
As part of the app installation process, the following fields will be created by default:
228+
Create the following Fields in collection sources both for logs and metrics. This ensures that your logs and metrics are tagged with relevant metadata, which the app dashboards require. For information on setting up Fields, see the [Fields](/docs/manage/fields) topic.
229229

230230
* `component`
231231
* `environment`
@@ -234,8 +234,6 @@ As part of the app installation process, the following fields will be created by
234234
* `db_cluster_address`
235235
* `db_cluster_port`
236236

237-
For information on setting up fields, see [Fields](/docs/manage/fields).
238-
239237
### Configuring or updating email notifications
240238

241239
If you haven’t enabled alerts and/or configured notifications through the Terraform procedure outlined above, we highly recommend enabling alerts of interest and configuring each enabled alert to send notifications to other people or services by [adding a monitor](/docs/alerts/monitors/create-monitor).
@@ -293,4 +291,4 @@ Existing customers have to perform the below steps:
293291
1. Add `db_cluster_address` and `db_cluster` port in their telegraf configuration as mentioned in the respective component’s collection doc. This is for tagging metrics.
294292
2. Add `db_cluster_address` and `db_cluster_port` in the Sumo Logic source for logs as mentioned in the respective component’s collection doc.
295293
3. Import the existing fields using fields.sh script in Step 4 and follow Step 1, 2, 3, and 5 under [Installation](#installation) to deploy the solution.
296-
4. The above step will deploy new dashboards and new monitors, so after migrating your custom content to these new dashboards, you can delete old FERs and dashboards.
294+
4. The above step will deploy new dashboards and new monitors, so after migrating your custom content to these new dashboards, you can delete old FERs and dashboards.

0 commit comments

Comments
 (0)