Service management for Aiven for Grafana®
Manage the lifecycle of your Aiven for Grafana® service, including power state, naming, tags, forks, cloud region, email sending, plugins, and advanced parameters.
Lifecycle changes and ongoing configuration
Service management for Aiven for Grafana® covers two kinds of changes. Lifecycle changes affect the service itself: powering it on or off, or deleting it, forking it, renaming it, or moving it to a different cloud or region. Configuration changes affect how the running service behaves: tags, advanced parameters, SMTP settings for outbound email, and the plugins available to your dashboards.
Most lifecycle changes trigger a status transition that you can follow from the service's Overview page, so look there to confirm a change has finished before you rely on the service again.
Before you start
- Backups underpin more than one lifecycle action: forking needs an existing backup on the source service, and powering off a service that has no backups permanently loses its data once the service is removed.
- Forking and renaming both produce a new service, so integrations, SSO configuration, and client connections tied to the original service need to be reattached manually afterward.
- For production services, enable termination protection so the service can't be
deleted by mistake. Use the
--enable-termination-protectionflag with theavn service updateoravn service createcommands.
Related pages