You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/integrations/amazon-aws/amazon-opensearch.md
+8-8Lines changed: 8 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,7 +12,7 @@ Amazon OpenSearch Service is a managed service that makes it easy to deploy, ope
12
12
13
13
The Sumo Logic app for Amazon OpenSearch collects CloudWatch logs, CloudWatch metrics, and CloudTrail logs, providing a unified logs and metrics app that provides insights into the operations and utilization of your OpenSearch service. The preconfigured dashboards help you monitor the key metrics by domain names and nodes, view the OpenSearch events for activities, and help you plan the capacity of your OpenSearch service.
account=* region=* namespace=aws/es domainname=* !nodeid=* metric=WriteLatency statistic = average | avg by domainname
195
195
```
196
196
197
-
## Collect logs and metrics for the Amazon OpenSearch app
197
+
## Collecting logs and metrics for the Amazon OpenSearch app
198
198
199
199
This section has instructions for collecting logs and metrics for the Amazon OpenSearch Service app.
200
200
201
-
### Collect CloudWatch Logs
201
+
### Collecting CloudWatch logs
202
202
203
203
To enable Amazon OpenSearch CloudWatch Logs, follow the steps mentioned in [AWS Documentation](https://docs.aws.amazon.com/opensearch-service/latest/developerguide/createdomain-configure-slow-logs.html)
204
204
@@ -218,7 +218,7 @@ Sumo Logic supports several methods for collecting logs from Amazon CloudWatch.
1. Add an [AWS CloudTrail Source](/docs/send-data/hosted-collectors/amazon-aws/aws-cloudtrail-source/) to your Hosted Collector.
224
224
* **Name**. Enter a name to display for the new Source.
@@ -236,21 +236,21 @@ Sumo Logic supports several methods for collecting logs from Amazon CloudWatch.
236
236
* **Enable Multiline Processing**. Select the **Detect messages spanning multiple lines** check box, and select **Infer Boundaries**.
237
237
2. Click **Save**.
238
238
239
-
### Collect CloudWatch Metrics
239
+
### Collecting CloudWatch metrics
240
240
241
241
1. Configure a [Hosted Collector](/docs/send-data/hosted-collectors/configure-hosted-collector/).
242
242
2. Configure an [Amazon CloudWatch Source for Metrics](/docs/send-data/hosted-collectors/amazon-aws/amazon-cloudwatch-source-metrics/) or [AWS Kinesis Firehose for Metrics Source](/docs/send-data/hosted-collectors/amazon-aws/aws-kinesis-firehose-metrics-source/) (Recommended).
243
243
3. **Namespaces**. Select **aws/es**.
244
244
4. **Metadata**. Add an account field to the source and assign it a value that is a friendly name/alias to your AWS account from which you are collecting metrics. The account field allows you to query metrics.
245
245
5. Click **Save**.
246
246
247
-
### Field in Field Schema
247
+
### Configure field in Field Schema
248
248
249
249
1. [New UI](/docs/get-started/sumo-logic-ui/). In the main Sumo Logic menu, select **Data Management**, and then under **Logs** select **Fields**. You can also click the **Go To...** menu at the top of the screen and select **Fields**. <br/>[Classic UI](/docs/get-started/sumo-logic-ui-classic/). In the main Sumo Logic menu, select **Manage Data > Logs > Fields**.
250
250
2. Search for the `domainname` field.
251
251
3. If not present, create it. Learn how to create and manage fields [here](/docs/manage/fields/#manage-fields).
252
252
253
-
### Field Extraction Rule(s)
253
+
### Configure Field Extraction Rule(s)
254
254
255
255
Create a Field Extraction Rule for CloudTrail Logs. Learn how to create a Field Extraction Rule [here](/docs/manage/field-extractions/create-field-extraction-rule/).
In case you have a centralized collection of CloudTrail logs and are ingesting them from all accounts into a single Sumo Logic CloudTrail log source, create the following Field Extraction Rule to map a proper AWS account(s) friendly name/alias. Create it if not already present or update it as required.
0 commit comments