Plugins 〉Amazon Managed Service for Prometheus
Amazon Managed Service for Prometheus
Amazon Managed Service for Prometheus Data Source
Amazon Managed Service for Prometheus is a Prometheus-compatible service that monitors and provides alerts on containerized applications and infrastructure at scale.
Read more about it here:
https://aws.amazon.com/prometheus/
Add the data source
- Configure this data source similar to the Prometheus data source.
- Configure AWS authentication with SigV4. Read these docs for more information on using AWS authentication in Grafana data sources. Read more about SigV4 here.
Migrate from core Prometheus to Amazon Managed Service for Prometheus
If you are using core Prometheus with SigV4 authentication, you must migrate to the Amazon Managed Service for Prometheus data source because SigV4 auth is deprecated in core Prometheus. This topic summarizes the steps required to migrate from core Prometheus to Amazon Managed Service for Prometheus.
- Get the
UID
for Prometheus using SigV4. - Get the
UID
for your new Amazon Managed Service for Prometheus. - Update dashboards with the new datasource
UID
. - Update alert rules by exporting provisioning files and updating the data source in the model or create new alert rules.
- Recreate correlations.
- Recreate recorded queries.
Migration instructions
Get the UID for the old and new data source.
- Navigate to the configuration page for your new data source.
- Find the
UID
in the url.- Example:
“connections/datasources/edit/<DATA SOURCE UID>”
- Example:
- Copy the UID for both the old and new data sources.
"<Prom SigV4 UID>"
"<AMP UID>"
Dashboard migration
- Navigate to the dashboard JSON panel of your dashboard that uses the old Prometheus with SigV4 authentication.
- Click on Dashboard settings.
- Select the JSON model in the tabs.
- Search for the
"<Prom SigV4 UID>"
.- Example:
"uid": "<Prom SigV4 UID>"
- Change both the
UID
and thetype
. - The old type is
prometheus
. - Example for changing
type
andUID
.
"type": "prometheus", "uid": "<Prom SigV4 UID>"
// can be change to
“type”: “grafana-amazonprometheus-datasource”, “uid”: “<AMP UID>”
- Example:
- Confirm the "datasource" change for all of the following categories in the JSON model.
annotations
panels
targets
templating
- Click “Save changes” in the bottom left side of the JSON model UI.
Save your dashboard.
Alert rules migration
- Alert rule data sources cannot be changed without wiping out the query.
- There are two ways to migrate alert rules.
- First, edit the rule by exporting to a provisioned file [documentation here].
- Navigate to the Alert rules page.
- Identify the alert rule that uses the Prom SigV4 data source.
- Select “Export rule.”
- Export the rule in your choice of JSON, YAML or Terraform.
- Search the exported rule for the
"<Prom SigV4 UID>"
. - Change the
UID
and thetype
in the exported rule.
"type": "prometheus", "uid": "<Prom SigV4 UID>"
// can be change to
“type”: “grafana-amazonprometheus-datasource”, “uid”: “<AMP UID>”
- Rename the rule and update the
name
field in the exported rule. - Delete the old rule.
- OR second, Create a new new alert rule documentation here.
- Copy the fields from the Prom SigV4 rule.
- Create a new alert rule and select your AMP data source.
- Add the fields from the old rule to the new rule.
- Delete the old rule.
- First, edit the rule by exporting to a provisioned file [documentation here].
Correlations migration
- Create a new correlation, see documentation here.
- Identify the correlation that uses the old Prom SigV4 data source.
- Copy the fields from your correlation.
- Create a brand new correlation using the new AMP data source.
- Add the fields from the old correlation to the new correlation.
- Delete the old correlation.
Recorded queries migration
- Only available in Grafana Enterprise and Grafana Cloud.
- Create a new recorded query, see documentation here.
- Identify the recorded query that uses the old Prom SigV4 data source.
- Copy the fields from your recorded query.
- Create a brand new recorded query using the new AMP data source.
- Add the fields from the old recorded query to the new recorded query.
- Delete the old recorded query.
Grafana Cloud Free
- Free tier: Limited to 3 users
- Paid plans: $55 / user / month above included usage
- Access to all Enterprise Plugins
- Fully managed service (not available to self-manage)
Self-hosted Grafana Enterprise
- Access to all Enterprise plugins
- All Grafana Enterprise features
- Self-manage on your own infrastructure
Grafana Cloud Free
- Free tier: Limited to 3 users
- Paid plans: $55 / user / month above included usage
- Access to all Enterprise Plugins
- Fully managed service (not available to self-manage)
Self-hosted Grafana Enterprise
- Access to all Enterprise plugins
- All Grafana Enterprise features
- Self-manage on your own infrastructure
Grafana Cloud Free
.h4 . .mb-0 }
- Free tier: Limited to 3 users
- Paid plans: $55 / user / month above included usage
- Access to all Enterprise Plugins
- Fully managed service (not available to self-manage)
Self-hosted Grafana Enterprise
- Access to all Enterprise plugins
- All Grafana Enterprise features
- Self-manage on your own infrastructure
Grafana Cloud Free
- Free tier: Limited to 3 users
- Paid plans: $55 / user / month above included usage
- Access to all Enterprise Plugins
- Fully managed service (not available to self-manage)
Self-hosted Grafana Enterprise
- Access to all Enterprise plugins
- All Grafana Enterprise features
- Self-manage on your own infrastructure
Grafana Cloud Free
- Free tier: Limited to 3 users
- Paid plans: $55 / user / month above included usage
- Access to all Enterprise Plugins
- Fully managed service (not available to self-manage)
Self-hosted Grafana Enterprise
- Access to all Enterprise plugins
- All Grafana Enterprise features
- Self-manage on your own infrastructure
Installing Amazon Managed Service for Prometheus on Grafana Cloud:
Installing plugins on a Grafana Cloud instance is a one-click install; same with updates. Cool, right?
Note that it could take up to 1 minute to see the plugin show up in your Grafana.
Installing plugins on a Grafana Cloud instance is a one-click install; same with updates. Cool, right?
Note that it could take up to 1 minute to see the plugin show up in your Grafana.
Installing plugins on a Grafana Cloud instance is a one-click install; same with updates. Cool, right?
Note that it could take up to 1 minute to see the plugin show up in your Grafana.
Installing plugins on a Grafana Cloud instance is a one-click install; same with updates. Cool, right?
Note that it could take up to 1 minute to see the plugin show up in your Grafana.
Installing plugins on a Grafana Cloud instance is a one-click install; same with updates. Cool, right?
Note that it could take up to 1 minute to see the plugin show up in your Grafana.
Installing plugins on a Grafana Cloud instance is a one-click install; same with updates. Cool, right?
Note that it could take up to 1 minute to see the plugin show up in your Grafana.
Installing plugins on a Grafana Cloud instance is a one-click install; same with updates. Cool, right?
Note that it could take up to 1 minute to see the plugin show up in your Grafana.
For more information, visit the docs on plugin installation.
Installing on a local Grafana:
For local instances, plugins are installed and updated via a simple CLI command. Plugins are not updated automatically, however you will be notified when updates are available right within your Grafana.
1. Install the Data Source
Use the grafana-cli tool to install Amazon Managed Service for Prometheus from the commandline:
grafana-cli plugins install
The plugin will be installed into your grafana plugins directory; the default is /var/lib/grafana/plugins. More information on the cli tool.
Alternatively, you can manually download the .zip file for your architecture below and unpack it into your grafana plugins directory.
Alternatively, you can manually download the .zip file and unpack it into your grafana plugins directory.
2. Configure the Data Source
Accessed from the Grafana main menu, newly installed data sources can be added immediately within the Data Sources section.
Next, click the Add data source button in the upper right. The data source will be available for selection in the Type select box.
To see a list of installed data sources, click the Plugins item in the main menu. Both core data sources and installed data sources will appear.
Changelog
1.0.2
- Bump dependencies
- github.com/grafana/grafana-aws-sdk from v0.30.0 to v0.31.3
- github.com/grafana/grafana-plugin-sdk-go v0.241.0 to v0.251.0
- @grafana/aws-sdk from 0.3.3 to 0.5.0
- @grafana/data from 11.1.0 to 11.2.2
- @grafana/e2e-selectors from 11.1.0 to 11.2.2
- @grafana/plugin-e2e from 1.3.2 to 1.8.3
- @grafana/experimental from 1.7.11 to 2.1.1
- @grafana/tsconfig from 1.3.0 to 2.0.0
- @grafana/prometheus from 11.1.0 to 11.2.2
- @grafana/runtime from 11.1.0 to 11.2.2
- @grafana/schema from 11.1.0 to 11.2.2
- @grafana/ui from 11.1.0 to 11.2.2
- @playwright/test from 1.44.1 to 1.47.2
- @swc/core from 1.5.25 to 1.7.28
- @swc/helpers from 0.5.11 to 0.5.13
- @testing-library/dom from 10.1.0 to 10.4.0
- @types/lodash from 4.17.4 to 4.17.10
- @typescript-eslint/eslint-plugin from 6.21.0 to 7.0.0
- cspell from 6.13.3 to 8.14.4
- eslint-plugin-import from 2.29.1 to 2.31.0
- eslint-plugin-jest from 28.5.0 to 28.8.1
- eslint-plugin-jsx-a11y from 6.8.0 to 6.10.0
- eslint-plugin-react-hooks from 4.6.0 to 4.6.2
- glob from 10.3.12 to 11.0.0
- prettier from 3.3.1 to 3.3.3
- sass from 1.77.4 to 1.79.3
- tslib from 2.5.3 to 2.7.0
- webpack from 5.91.0 to 5.95.0
- Update links to documentation in the Config Editor
1.0.1
- Fix sigv4 auth in Cloud
1.0.0
- Initial public release
0.3.0
- Rename plugin & repo
0.2.0 (Private release for testing)
- Initial private release of the Amazon Managed Prometheus plugin, a wrapper around the core Prometheus datasource that uses Amazon-specific authentication.
0.1.0 (Unreleased)
Initial release.