Skip to content

Commit 9d21959

Browse files
authored
Update amazon-bedrock.md
1 parent 53c0b69 commit 9d21959

File tree

1 file changed

+6
-8
lines changed

1 file changed

+6
-8
lines changed

docs/integrations/amazon-aws/amazon-bedrock.md

Lines changed: 6 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -179,7 +179,6 @@ The Amazon Bedrock app uses the following logs and metrics:
179179

180180
### Sample queries
181181

182-
183182
```sql title="Successful Event Locations (CloudTrail log based)"
184183
account=* region=us-east-1 namespace=aws/bedrock "\"eventSource\":\"bedrock.amazonaws.com\"" !errorCode
185184
| json "eventSource", "eventName", "eventType", "sourceIPAddress", "errorCode", "errorMessage" nodrop
@@ -264,7 +263,7 @@ account=* region=* namespace=aws/bedrock modelid=* metric=Invocations statistic=
264263

265264
## Collecting logs and metrics for the Amazon Bedrock app
266265

267-
### Collect CloudWatch Metrics
266+
### CloudWatch metrics collection
268267

269268
Sumo Logic supports collecting metrics using two source types:
270269

@@ -274,7 +273,7 @@ Sumo Logic supports collecting metrics using two source types:
274273
* Namespace for **Amazon Bedrock** Service is **AWS/Bedrock**.
275274
* ​​​**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”.
276275

277-
### Collect Amazon Bedrock CloudTrail logs
276+
### Amazon Bedrock CloudTrail logs collection
278277

279278
1. Add an [AWS CloudTrail Source](/docs/send-data/hosted-collectors/amazon-aws/aws-cloudtrail-source.md) to your Hosted Collector.
280279
* **Name**. Enter a name to display the new Source.
@@ -292,7 +291,7 @@ Sumo Logic supports collecting metrics using two source types:
292291
* **Enable Multiline Processing**. Select the **Detect messages spanning multiple lines** check box, and select **Infer Boundaries**.
293292
2. Click **Save**.
294293

295-
### Collect Amazon Bedrock CloudWatch logs
294+
### Amazon Bedrock CloudWatch logs collection
296295

297296
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)
298297

@@ -302,7 +301,6 @@ Ensure that when configuring `CloudWatch Logs`, the log group name follows the p
302301

303302
<img src={useBaseUrl('img/integrations/amazon-aws/Amazon-Bedrock-Settings.png')} alt="Amazon Bedrock Setting" style={{border: '1px solid gray'}} />
304303

305-
306304
Sumo Logic supports several methods for collecting logs from Amazon CloudWatch. You can choose either of them to collect logs:
307305

308306
- **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.
315313

316314
<img src={useBaseUrl('https://sumologic-app-data-v2.s3.amazonaws.com/dashboards/AWS-Lambda/lamda-cw-logs-source-fields.png')} alt="Fields" />
317315

318-
### Field in Field Schema
316+
### Configure field in field schema
319317

320318
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**.
321319
1. Search for the `modelId` field.
322320
1. If not present, create it. Learn how to create and manage fields [here](/docs/manage/fields#manage-fields).
323321

324-
### Field Extraction Rule(s)
322+
### Configure Field Extraction Rule(s)
325323

326324
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).
327325

@@ -357,7 +355,7 @@ if (isEmpty(namespace),"unknown",namespace) as namespace
357355
| fields namespace, modelId
358356
```
359357
360-
### Centralized AWS CloudTrail log collection
358+
### Centralized AWS CloudTrail logs collection
361359
362360
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.
363361

0 commit comments

Comments
 (0)