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
## Collecting logs and metrics for the Amazon Bedrock app
266
265
267
-
### Collect CloudWatch Metrics
266
+
### CloudWatch metrics collection
268
267
269
268
Sumo Logic supports collecting metrics using two source types:
270
269
@@ -274,7 +273,7 @@ Sumo Logic supports collecting metrics using two source types:
274
273
* Namespace for **Amazon Bedrock** Service is **AWS/Bedrock**.
275
274
* **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. Metrics can be queried via the “account field”.
276
275
277
-
### Collect Amazon Bedrock CloudTrail logs
276
+
### Amazon Bedrock CloudTrail logs collection
278
277
279
278
1. Add an [AWS CloudTrail Source](/docs/send-data/hosted-collectors/amazon-aws/aws-cloudtrail-source.md) to your Hosted Collector.
280
279
***Name**. Enter a name to display the new Source.
@@ -292,7 +291,7 @@ Sumo Logic supports collecting metrics using two source types:
292
291
***Enable Multiline Processing**. Select the **Detect messages spanning multiple lines** check box, and select **Infer Boundaries**.
293
292
2. Click **Save**.
294
293
295
-
### Collect Amazon Bedrock CloudWatch logs
294
+
### Amazon Bedrock CloudWatch logs collection
296
295
297
296
To enable Amazon Bedrock CloudWatch Logs, follow the steps mentioned in [AWS Documentation](https://docs.aws.amazon.com/bedrock/latest/userguide/model-invocation-logging.html)
298
297
@@ -302,7 +301,6 @@ Ensure that when configuring `CloudWatch Logs`, the log group name follows the p
Sumo Logic supports several methods for collecting logs from Amazon CloudWatch. You can choose either of them to collect logs:
307
305
308
306
-**AWS Kinesis Firehose for Logs**. Configure an [AWS Kinesis Firehose for Logs](/docs/send-data/hosted-collectors/amazon-aws/aws-kinesis-firehose-logs-source/#create-an-aws-kinesis-firehose-for-logssource) (Recommended); or
@@ -315,13 +313,13 @@ Sumo Logic supports several methods for collecting logs from Amazon CloudWatch.
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**.
321
319
1. Search for the `modelId` field.
322
320
1. If not present, create it. Learn how to create and manage fields [here](/docs/manage/fields#manage-fields).
323
321
324
-
### Field Extraction Rule(s)
322
+
### Configure Field Extraction Rule(s)
325
323
326
324
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).
327
325
@@ -357,7 +355,7 @@ if (isEmpty(namespace),"unknown",namespace) as namespace
357
355
| fields namespace, modelId
358
356
```
359
357
360
-
### Centralized AWS CloudTrail log collection
358
+
### Centralized AWS CloudTrail logs collection
361
359
362
360
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 / update it as required.
0 commit comments