Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: spelling mistake and rewording #196

Merged
merged 1 commit into from
Dec 18, 2024
+4 −4
Merged

fix: spelling mistake and rewording #196

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/en/guides/cost/cost-visualization/amazon-prometheus.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@ Amazon Managed Service for Prometheus cost and usage visuals will allow you to g

To visualize and analyze the cost and usage data, you need to create a custom Athena view.

1. Before proceeding, make sure that you’ve created the CUR (step #1) and deployed the AWS Conformation Template (step #2) mentioned in the [Implementation overview][cid-implement].
1. Before proceeding, make sure that you’ve created the CUR (step #1) and deployed the AWS CloudFormation Template (step #2) mentioned in the [Implementation overview][cid-implement].

2. Now, Create a new Amazon Athena [view][view] by using the following query. This query fetches cost and usage of Amazon Managed Service for Prometheus across all the AWS Accounts in your Organization.

Expand Down
6 changes: 3 additions & 3 deletions docs/en/guides/operational/adot-at-scale/operating-adot-collector.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -78,9 +78,9 @@ The same architecture can also be used for collecting traces. In this case, inst
**Advantages**

* Minimal scaling concerns
* Configuring High-Availability is a challenge
* Too many copies of Collector in use
* Can be easy for Logs support
* High availability configuration options
* Flexibility in Collector deployment
* Simplified log support process

**Disadvantages**

Expand Down
Loading