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.

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

CloudWatch: Make it possible to specify custom api endpoint #31402

Merged
merged 11 commits into from
Feb 24, 2021

Conversation

sunker
Copy link
Contributor

@sunker sunker commented Feb 22, 2021

Tested using monitoring.us-east-2.amazonaws.com and it works fine. Info about api endpoints and why to use them can be found here

All the other AWS data source plugins that we have, i.e IOT Sitewise, Timestream and X-Ray, already have support for specifying a custom endpoint.

Fixes #26041

@sunker sunker added this to the 7.5.0 milestone Feb 22, 2021
@sunker sunker requested a review from aknuds1 February 22, 2021 16:26
@sunker sunker requested a review from a team as a code owner February 22, 2021 16:26
@sunker sunker requested a review from a team as a code owner February 22, 2021 16:26
@sunker sunker requested review from a team, dsotirakis, oddlittlebird, achatterjee-grafana, osg-grafana and ivanahuckova and removed request for a team, dsotirakis and ivanahuckova February 22, 2021 16:26
Copy link
Contributor

@achatterjee-grafana achatterjee-grafana left a comment

Choose a reason for hiding this comment

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

Added minor copy-edit suggestions.

docs/sources/datasources/cloudwatch.md Outdated Show resolved Hide resolved
sunker and others added 2 commits February 23, 2021 08:40
Co-authored-by: achatterjee-grafana <70489351+achatterjee-grafana@users.noreply.github.com>
…or.tsx

Co-authored-by: achatterjee-grafana <70489351+achatterjee-grafana@users.noreply.github.com>
docs/sources/datasources/cloudwatch.md Outdated Show resolved Hide resolved
pkg/tsdb/cloudwatch/cloudwatch.go Outdated Show resolved Hide resolved
sunker and others added 2 commits February 23, 2021 10:33
Co-authored-by: Arve Knudsen <arve.knudsen@gmail.com>
sunker and others added 3 commits February 23, 2021 12:01
Copy link
Contributor

@osg-grafana osg-grafana left a comment

Choose a reason for hiding this comment

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

Unblocking (if I was blocking this PR) with an Approve

@achatterjee-grafana
Copy link
Contributor

Good catch, "documentation" word was missing and it is needed here.

@sunker sunker merged commit 0555908 into master Feb 24, 2021
@sunker sunker deleted the sunker/26041-aws-custom-endpoint branch February 24, 2021 15:05
@bitbier
Copy link

bitbier commented Dec 1, 2021

I actually commented on the wrong PR, but I don't think this will work for both metrics and logs or there should be a documented caveat on that.

Cloudwatch Metrics and Cloudwatch Logs both use different endpoints monitoring.us-east-2.amazonaws.com and logs.us-east-2.amazonaws.com respectively; however, the datasource mixes both metrics and logs into one datasource. I think the current workaround here is to create two separate CloudWatch datasources (one for metrics and one for logs) if you want override the endpoint here.

@yarons
Copy link

yarons commented Mar 1, 2023

We ran into this problem as well but adding to different data sources still leads to an error and the data is not fetched.
Described in #63420.

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

Successfully merging this pull request may close these issues.

Cloudwatch: Custom endpoint URL in CloudWatch data source
6 participants