Documentation for automated readers
A curated documentation index is available at: https://grafana.com/llms.txt
A complete documentation index is available at: https://grafana.com/llms-full.txt
These indexes can help with page discovery before fetching individual documents.
This page is also available in Markdown, which may be easier for automated readers and AI tools to parse than HTML. The Markdown version is available at https://grafana.com/docs/grafana-cloud/observe-and-act/alert-and-measure-reliability/service-center/create-a-service.md, or by sending Accept: text/markdown to https://grafana.com/docs/grafana-cloud/observe-and-act/alert-and-measure-reliability/service-center/create-a-service/. For broader documentation discovery, the curated index is available at https://grafana.com/llms.txt and the complete index is available at https://grafana.com/llms-full.txt.
Create a service
Create a service to enable the Service center view and provide a centralized operational view of your team’s services.
A service represents an application, API, or other component that your team owns and operates. Service center correlates Grafana Cloud resources to a service by matching labels and tags that identify that service.
You can create and manage services directly in Grafana Cloud, provision them with Terraform, or import them from Backstage.
Add a service
To create a service in Grafana Cloud, navigate to Alerts & IRM > Service center and click + New Service.
Set name and attributes
Configure the basic information for the service:
Enter a name for the service.
Optional: Enter a description of the service.
Optional: Assign a team to the service to enable on-call information and respond to service issues from Service center.
Optional: Enter custom attributes using Add Attribute.
Attributes provide additional context about the service. Common examples include links to Documentation, Repository, and other relevant metadata.
Configure service content
In the Service content section, define how Service center identifies resources associated with the service.
- Service identifier defines the value of the
service_namelabel used to discover related resources such as incidents, SLOs, dashboards, synthetic checks, and alert rules. - Additional identifier lets you define additional label key-value pairs when resources use another label convention.

Note
The Service identifier value cannot be changed after the service is created.
Configure dependencies
Optionally, define dependencies between services to model relationships within your system architecture. Dependencies help assess potential upstream or downstream impact during incidents.
After you save the service, Service center discovers matching resources and displays them in the Service center view.
Provision services with Terraform
You can also manage services as code with the Grafana Terraform provider, which lets you version service definitions and keep them alongside the teams, SLOs, and alert rules they relate to.
For instructions, refer to Provision services using Terraform.
Import services from Backstage
If you use Backstage, you can import services from your software catalog and keep them synchronized with Service center.
Imported services are automatically correlated with Grafana Cloud resources such as incidents, SLOs, and other operational data.
To configure the integration, follow the instructions for the backstage-plugin-grafana-catalog.
Was this page helpful?
Related resources from Grafana Labs


