Skip to content

Conversation

@Apoorvkudesia-sumologic
Copy link
Collaborator

@Apoorvkudesia-sumologic Apoorvkudesia-sumologic commented Jan 2, 2026

Purpose of this pull request

Select the type of change

  • Minor Changes - Typos, formatting, slight revisions
  • Update Content - Revisions, updating sections
  • New Content - New features, sections, pages, tutorials
  • Site and Tools - .clabot, version updates, maintenance, dependencies, new packages for the site (Docusaurus, Gatsby, React, etc.)

Ticket (if applicable)

@cla-bot cla-bot bot added the cla-signed Contributor approved, listed in .clabot file label Jan 2, 2026
Copy link
Collaborator

@jpipkin1 jpipkin1 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@Apoorvkudesia-sumologic, this pull request looks pretty good, except for some broken links and missing screen images. After you fix those, I'll give this one another look.

@sumoanema sumoanema added the do-not-merge Pull requests that should not be merged label Jan 5, 2026
* Configure an [AWS Kinesis Firehose for Metrics Source](/docs/send-data/hosted-collectors/amazon-aws/aws-kinesis-firehose-metrics-source) (Recommended); or
* Configure an [Amazon CloudWatch Source for Metrics](/docs/send-data/hosted-collectors/amazon-aws/amazon-cloudwatch-source-metrics)

* Namespace for **Amazon Sagemaker** Service is **AWS/Sagemaker**.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There are multiple namespaces for could watch metrics. I think we should list all ?


### Configure field in field schema

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**.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this required. This seems to be copied from bedrock since it has modelId ? Also since we are creating all the fields using fields.tf - is any manual creation even required ?


As part of the app installation process, the following fields will be created by default:

* `account`: The friendly name or alias assigned to the AWS account.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We need to reconsider the fields which will get created automatically. Since some of these fields are not needed to be created explicitly

| if (!isBlank(endpointname), endpointname, endpointconfigname) as endpoint
| fields accountid, region, namespace, endpoint
```

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We also had a metric rule which needs to be in place in this doc.


## Viewing the Sagemaker dashboards

We highly recommend you view these dashboards in the [AWS Observability view](/docs/dashboards/explore-view/#aws-observability) of the AWS Observability solution.
Copy link
Collaborator

@sumoanema sumoanema Jan 5, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Will this be possible as of now ? Since this is not part of aws observability

Copy link
Collaborator

@jpipkin1 jpipkin1 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approved, @Apoorvkudesia-sumologic. I made some small updates (see commits "Updates from review" and "Add Amazon Sagemaker to product list").

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

cla-signed Contributor approved, listed in .clabot file do-not-merge Pull requests that should not be merged

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants