updating FER section

Author: chetanchoudhary-sumo

docs/integrations/amazon-aws/dynamodb.md

@@ -113,20 +113,7 @@ The “**tablename**” field will be created.
 
 ### Field Extraction Rule(s)
 
-Create Field Extraction Rule for CloudTrail Logs. Learn how to create Field Extraction Rule [here](/docs/manage/field-extractions/create-field-extraction-rule).
-
-```sql
-Rule Name: AwsObservabilityDynamoDBCloudTrailLogsFER
-Applied at: Ingest Time
-Scope (Specific Data):
-account=* eventname eventsource "dynamodb.amazonaws.com"
-Parse Expression:
-| json "eventSource", "awsRegion", "requestParameters.tableName", "recipientAccountId" as eventSource, region, tablename, accountid nodrop
-| where eventSource = "dynamodb.amazonaws.com"
-| "aws/dynamodb" as namespace
-| tolowercase(tablename) as tablename
-| fields region, namespace, tablename, accountid
-```
+Field Extraction Rule for CloudTrail Logs are automatically created for Database Application Components named as **AwsObservabilityDynamoDBCloudTrailLogsFER**.
 
 
 ### Centralized AWS CloudTrail Log Collection

docs/integrations/databases/cassandra.md

@@ -263,26 +263,7 @@ Pivoting to Tracing data from Entity Inspector is possible only for “Cassandra
    5. Sumo Logic Kubernetes collection will automatically start collecting logs from the pods having the annotations defined above.
    6. Verify logs in Sumo Logic.
 
-3. Add an 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, we need to create a Field Extraction Rule if not already created for Proxy Application Components. This step is not needed if one is using application components solution terraform script. To do so:
-   1. [**Classic UI**](/docs/get-started/sumo-logic-ui-classic). In the main Sumo Logic menu, select **Manage Data > Logs > Field Extraction Rules**. <br/>[**New UI**](/docs/get-started/sumo-logic-ui). In the top menu select **Configuration**, and then under **Logs** select **Field Extraction Rules**. You can also click the **Go To...** menu at the top of the screen and select **Field Extraction Rules**.  
-   2. Click the **+ Add** button on the top right of the table.
-   3. The **Add Field Extraction Rule** form will appear:
-4. Enter the following options:
-   * **Rule Name**. Enter the name as **App Observability - Database**.
-   * **Applied At.** Choose **Ingest Time**
-   * **Scope**. Select **Specific Data**
-   * **Scope**: Enter the following keyword search expression:  
-    ```sql
-    pod_labels_environment=* pod_labels_component=database pod_labels_db_system=* pod_labels_db_cluster=*
-    ```
-   * **Parse Expression**. Enter the following parse expression:
-   ```sql
-   if (!isEmpty(pod_labels_environment), pod_labels_environment, "") as environment
-   | pod_labels_component as component
-   | pod_labels_db_system as db_system
-   | if (!isEmpty(pod_labels_db_cluster), pod_labels_db_cluster, null) as db_cluster
-   ```
-5. Click **Save** to create the rule.
+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, we will have Field Extraction Rule automatically created for Database Application Components named as **AppObservabilityCassandraDatabaseFER**.
 
 </TabItem>
 <TabItem value="non-k8s">

docs/integrations/databases/couchbase.md

@@ -199,28 +199,7 @@ This section explains the steps to collect Couchbase logs from a Kubernetes envi
     ```
    5. Sumo Logic Kubernetes collection will automatically start collecting logs from the pods having the annotations defined above.
    6. Verify logs in Sumo Logic.
-3. **Add a FER to normalize the fields in Kubernetes environments**. This step is not needed if using application components solution terraform script. Labels created in Kubernetes environments automatically are prefixed with pod_labels. To normalize these for our app to work, we need to create a Field Extraction Rule if not already created for Proxy Application Components. To do so:
-   1. [**Classic UI**](/docs/get-started/sumo-logic-ui-classic). In the main Sumo Logic menu, select **Manage Data > Logs > Field Extraction Rules**. <br/>[**New UI**](/docs/get-started/sumo-logic-ui). In the top menu select **Configuration**, and then under **Logs** select **Field Extraction Rules**. You can also click the **Go To...** menu at the top of the screen and select **Field Extraction Rules**.  
-   2. Click the **+ Add Rule** button on the top right of the table.
-   3. The **Add Field Extraction Rule** form will appear:
-   4. Enter the following options:
-      * **Rule Name**. Enter the name as **App Observability - Proxy**.
-      * **Applied At.** Choose **Ingest Time**
-      * **Scope**. Select **Specific Data**
-      * **Scope**: Enter the following keyword search expression:  
-      ```sql
-      pod_labels_environment=* pod_labels_component=database \
-      pod_labels_db_cluster=* pod_labels_db_system=*
-      ```
-      * **Parse Expression**. Enter the following parse expression:
-      ```sql
-      if (!isEmpty(pod_labels_environment), pod_labels_environment, "") as environment
-      | pod_labels_component as component
-      | pod_labels_db_system as db_system
-      | pod_labels_db_cluster as db_cluster
-      | if (!isEmpty(pod_labels_db_cluster), pod_labels_db_cluster, null) as db_cluster
-      ```
-   5. Click **Save** to create the rule.
+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, we will have Field Extraction Rule automatically created for Database Application Components named as **AppObservabilityCouchbaseDatabaseFER**.
 
 </TabItem>
 <TabItem value="non-k8s">

docs/integrations/databases/mariadb.md

@@ -200,27 +200,7 @@ This section explains the steps to collect MariaDB logs from a Kubernetes enviro
     ```
    5. Sumo Logic Kubernetes collection will automatically start collecting logs from the pods having the annotations defined above.
    6. Verify logs in Sumo Logic.
-3. **Add an FER to normalize the fields in Kubernetes environments**. This step is not needed if using application components solution terraform script. Labels created in Kubernetes environments automatically are prefixed with pod_labels. To normalize these for our app to work, we need to create a Field Extraction Rule if not already created for Proxy Application Components:
-   1. [**Classic UI**](/docs/get-started/sumo-logic-ui-classic). In the main Sumo Logic menu, select **Manage Data > Logs > Field Extraction Rules**. <br/>[**New UI**](/docs/get-started/sumo-logic-ui). In the top menu select **Configuration**, and then under **Logs** select **Field Extraction Rules**. You can also click the **Go To...** menu at the top of the screen and select **Field Extraction Rules**.  
-   2. Click the **+ Add** button on the top right of the table.
-   3. The **Add Field Extraction Rule** form will appear:
-   4. Enter the following options:
-      * **Rule Name**. Enter the name as **App Observability - database**.
-      * **Applied At.** Choose **Ingest Time**
-      * **Scope**. Select **Specific Data**
-      * **Scope**. Enter the following keyword search expression:
-      ```sql
-      pod_labels_environment=* pod_labels_component=database
-      pod_labels_db_cluster=* pod_labels_db_system=*
-      ```
-      * **Parse Expression**. Enter the following parse expression:
-      ```sql
-      if (!isEmpty(pod_labels_environment), pod_labels_environment, "") as environment
-       | pod_labels_component as component
-       | pod_labels_db_system as db_system
-       | if (!isEmpty(pod_labels_db_cluster), pod_labels_db_cluster, null) as db_cluster
-      ```
-   5. Click **Save** to create the rule.
+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, we will have Field Extraction Rule automatically created for Database Application Components named as **AppObservabilityMariaDBDatabaseFER**.
 
 
 </TabItem>

docs/integrations/databases/memcached.md

@@ -217,27 +217,7 @@ This section explains the steps to collect Memcached logs from a Kubernetes envi
     kubectl describe pod <Memcached_pod_name>
     ```
    4. Sumo Logic Kubernetes collection will automatically start collecting logs from the pods having the annotations defined above.
-3. **Add a FER to normalize the fields in Kubernetes environments**. This step is not needed if one is using application components solution terraform script. Labels created in Kubernetes environments automatically are prefixed with pod_labels. To normalize these for our app to work, we need to create a Field Extraction Rule if not already created for Proxy Application Components. To do so:
-   1. [**Classic UI**](/docs/get-started/sumo-logic-ui-classic). In the main Sumo Logic menu, select **Manage Data > Logs > Field Extraction Rules**. <br/>[**New UI**](/docs/get-started/sumo-logic-ui). In the top menu select **Configuration**, and then under **Logs** select **Field Extraction Rules**. You can also click the **Go To...** menu at the top of the screen and select **Field Extraction Rules**.  
-   2. Click the + Add button on the top right of the table.
-   3. The **Add Field Extraction Rule** form will appear:
-   4. Enter the following options:
-     * **Rule Name**. Enter the name as **App Observability - Database**.
-     * **Applied At**. Choose **Ingest Time**
-     * **Scope**. Select **Specific Data**
-     * **Scope**: Enter the following keyword search expression:
-     ```sql
-     pod_labels_environment=* pod_labels_component=database \
-     pod_labels_db_system=* pod_labels_db_cluster=*
-     ```
-     * **Parse Expression**. Enter the following parse expression:
-     ```sql
-     if (!isEmpty(pod_labels_environment), pod_labels_environment, "") as environment
-     | pod_labels_component as component
-     | pod_labels_db_system as db_system
-     | if (!isEmpty(pod_labels_db_cluster), pod_labels_db_cluster, null) as db_cluster
-     ```
-   5. Click **Save** to create the rule.
+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, we will have Field Extraction Rule automatically created for Database Application Components named as **AppObservabilityMemcachedDatabaseFER**.
 
 </TabItem>
 <TabItem value="non-k8s">

docs/integrations/databases/mongodb.md

@@ -234,27 +234,8 @@ Pivoting to Tracing data from Entity Inspector is possible only for “MongoDB a
      kubectl describe pod <MongoDB_pod_name>
      ```
    5. Sumo Logic Kubernetes collection will automatically start collecting logs from the pods having the annotations defined above.
-3. **Add an FER to normalize the fields in Kubernetes environments**. This step is not needed if one is using application components solution terraform script. Labels created in Kubernetes environments automatically are prefixed with `pod_labels`. To normalize these for our app to work, we need to create a Field Extraction Rule if not already created for Database Application Components. To do so:
-   1. [**Classic UI**](/docs/get-started/sumo-logic-ui-classic). In the main Sumo Logic menu, select **Manage Data > Logs > Field Extraction Rules**. <br/>[**New UI**](/docs/get-started/sumo-logic-ui). In the top menu select **Configuration**, and then under **Logs** select **Field Extraction Rules**. You can also click the **Go To...** menu at the top of the screen and select **Field Extraction Rules**.  
-   2. Click the + Add button on the top right of the table.
-   3. The **Add Field Extraction Rule** form will appear:
-   4. Enter the following options:
-     * **Rule Name**. Enter the name as **App Observability - Database**.
-     * **Applied At**. Choose **Ingest Time**
-     * **Scope**. Select **Specific Data**
-     * **Scope**: Enter the following keyword search expression:
-      ```sql
-      pod_labels_environment=* pod_labels_component=database \
-      pod_labels_db_system=* pod_labels_db_cluster=*
-      ```
-     * **Parse Expression**.Enter the following parse expression:
-      ```sql
-      | if (!isEmpty(pod_labels_environment), pod_labels_environment, "") as environment
-      | pod_labels_component as component
-      | pod_labels_db_system as db_system
-      | pod_labels_db_cluster as db_cluster
-      ```
-4. Click **Save** to create the rule.
+   
+   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, we will have Field Extraction Rule automatically created for Database Application Components named as **AppObservabilityMongoDBDatabaseFER**.
 
 </TabItem>
 <TabItem value="non-k8s">

docs/integrations/databases/mysql.md

@@ -345,29 +345,7 @@ Sumo Logic Kubernetes collection will automatically start collecting logs from t
 
 </details>
 
-2. **Add an FER to normalize the fields in Kubernetes environments**. This step is not needed if using application components solution terraform script. Labels created in Kubernetes environments are automatically prefixed with pod_labels. To normalize these for our app to work, we'll create a [Field Extraction Rule](/docs/manage/field-extractions/create-field-extraction-rule), Database Application Components, assuming it does not already exist:
-   1. [**Classic UI**](/docs/get-started/sumo-logic-ui-classic). In the main Sumo Logic menu, select **Manage Data > Logs > Field Extraction Rules**. <br/>[**New UI**](/docs/get-started/sumo-logic-ui). In the top menu select **Configuration**, and then under **Logs** select **Field Extraction Rules**. You can also click the **Go To...** menu at the top of the screen and select **Field Extraction Rules**.  
-   2. Click the **+ Add**.
-   3. The **Add Field Extraction** pane appears.
-   4. **Rule Name.** Enter "App Observability - Database".
-   5. **Applied At**. Choose "Ingest Time".
-   6. **Scope**. Select "Specific Data".
-     * **Scope**. Enter the following keyword search expression:  
-      ```sql
-      pod_labels_environment=* pod_labels_component=database pod_labels_db_system=* pod_labels_db_cluster=*
-      ```
-     * **Parse Expression**. Enter the following parse expression:
-     ```sql
-     | if (!isEmpty(pod_labels_environment), pod_labels_environment, "") as environment
-     | pod_labels_component as component
-     | pod_labels_db_system as db_system
-     | if (!isEmpty(pod_labels_db_cluster), pod_labels_db_cluster, null) as db_cluster
-     ```
-   7. Click **Save** to create the rule.
-   8. To verify that logs are flowing into Sumo Logic, run this query:
-    ```sql
-    component=database db_system=mysql db_cluster=<your_mysql_cluster_name>
-    ```
+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, we will have Field Extraction Rule automatically created for Database Application Components named as **AppObservabilityMySQLDatabaseFER**.
 
 </TabItem>
 <TabItem value="non-k8s">

docs/integrations/databases/oracle.md

@@ -252,27 +252,7 @@ annotations:
 2. The Sumo Logic Kubernetes collection will automatically start collecting logs from the pods having the annotations defined above.
 3. Verify logs in Sumo Logic.
 
-**Add an FER to normalize the fields in Kubernetes environments**
-
-This step is not needed if you're using application components solution terraform script. Labels created in Kubernetes environments automatically are prefixed with pod_labels. To normalize these for our app to work, we need to create a Field Extraction Rule if not already created for Proxy Application Components. To do so:
-1. [**Classic UI**](/docs/get-started/sumo-logic-ui-classic). In the main Sumo Logic menu, select **Manage Data > Logs > Field Extraction Rules**. <br/>[**New UI**](/docs/get-started/sumo-logic-ui). In the top menu select **Configuration**, and then under **Logs** select **Field Extraction Rules**. You can also click the **Go To...** menu at the top of the screen and select **Field Extraction Rules**.  
-1. Click the **+Add** button on the top right of the table.
-1. The **Add Field Extraction Rule** form will appear. Enter the following options:
-   1. **Rule Name**. Enter the name as **App Observability - database**.
-   2. **Applied At**. Choose **Ingest Time**.
-   3. **Scope**. Select **Specific Data**.
-   4. **Scope**: Enter the following keyword search expression.
-   ```sql
-   pod_labels_environment=* pod_labels_component=database pod_labels_db_cluster=* pod_labels_db_system=*
-   ```
-   5. **Parse Expression**. Enter the following parse expression.
-   ```sql
-   if (!isEmpty(pod_labels_environment), pod_labels_environment, "") as environment
-   | pod_labels_component as component
-   | pod_labels_db_system as db_system
-   | if(!isEmpty(pod_labels_db_cluster), pod_labels_db_cluster, null) as db_cluster
-   ```
-1. Click **Save** to create the rule.
+**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, we will have Field Extraction Rule automatically created for Database Application Components named as **AppObservabilityOracleDatabaseFER**.
 
 </TabItem>
 <TabItem value="non-k8s">

docs/integrations/databases/redis.md

@@ -244,25 +244,7 @@ This section explains the steps to collect Redis logs from a Kubernetes environm
     kubectl describe pod <redis_pod_name>
     ```
    5. Sumo Logic Kubernetes collection will automatically start collecting logs from the pods having the annotations defined above.
-3. **Add an FER to normalize the fields in Kubernetes environments**. This step is not needed if using application components solution terraform script. Labels created in Kubernetes environments automatically are prefixed with `pod_labels`. To normalize these for our app to work, we need to create a Field Extraction Rule. To do so:
-   * [**Classic UI**](/docs/get-started/sumo-logic-ui-classic). In the main Sumo Logic menu, select **Manage Data > Logs > Field Extraction Rules**. <br/>[**New UI**](/docs/get-started/sumo-logic-ui). In the top menu select **Configuration**, and then under **Logs** select **Field Extraction Rules**. You can also click the **Go To...** menu at the top of the screen and select **Field Extraction Rules**.  
-   * Click the + Add button on the top right of the table.
-   * The **Add Field Extraction Rule** form will appear:
-   * Enter the following options:
-      * **Rule Name**. Enter the name as **App Observability - Database**.
-      * **Applied At**. Choose **Ingest Time**.
-        * **Scope**. Select **Specific Data**. Enter the following keyword search expression:
-         ```sql
-         pod_labels_environment=* pod_labels_component=database pod_labels_db_system=* pod_labels_db_cluster=*
-         ```
-        * **Parse Expression**. Enter the following parse expression:
-         ```sql
-         | if (!isEmpty(pod_labels_environment), pod_labels_environment, "") as environment
-            | pod_labels_component as component
-            | pod_labels_db_system as db_system
-            | if (!isEmpty(pod_labels_db_cluster), pod_labels_db_cluster, null) as db_cluster
-         ```    
-   * Click **Save** to create the rule.
+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, we will have Field Extraction Rule automatically created for Database Application Components named as **AppObservabilityRedisDatabaseFER**.
 
 </TabItem>
 <TabItem value="non-k8s">