Create a service

Reading time: 0 minute(s) (0 words)

See how to create a service in Nobl9

In Nobl9, services are organized under projects. Creating a service is the first step toward effective SLO configuration and service monitoring. A service represents a logical entity, such as:

• An internal or external API
• A database
• Any other endpoint you care about setting an SLO for, like a user journey

Simply put, a service is something you want to monitor and test for reliability.

You need at least one service to create SLOs in Nobl9.

A service can have one or more SLOs defined for it. Every SLO created in Nobl9 must be tied to a service.

Additionally, a single service in Nobl9 can include other dependent services, making it easier to track and manage your entire infrastructure.

Step-by-step

To create a service on the Nobl9 Web:

1. Go to Catalog > Services.
2. Click .
3. Select a Project.
   Specifying a project is helpful when multiple users are spread across multiple teams or projects. When the Project field is left blank, Nobl9 uses the default project.
4. Enter a Display Name.
   You can enter a user-friendly name with spaces in this field.
5. Enter a Name.
   The name is mandatory and can only contain lowercase, alphanumeric characters, and dashes (for example, my-project-1). Nobl9 duplicates the display name here, transforming it into the supported format, but you can edit the result.
6. Select or add Labels.
   Labels have a specific format and must conform to the following rules:
   

   • key: value format
   • key can contain only lowercase alphanumeric characters, underscores, and dashes; must start with a letter and end with an alphanumeric character; maximum length 63 characters
   • value can contain Unicode characters; maximum length 200 characters
   • Maximum of 20 labels attached
7. Enter a Description.
   Here you can add details such as who is responsible for the integration (team/owner) and the purpose of creating it.
8. Click Create service.

Creating a service

Tips on naming and structuring

For example, in an e-commerce application, an Order processing service might handle customer orders. This service could rely on multiple other components, such as:

Supply orchestration to track in-progress order allocation and traceability of supply chain events

Payments to track transaction processing

Notifications to monitor order processing communication

Shipping coordination to monitor scheduling and track delivery updates

These supporting components can also be defined as individual services in Nobl9, enabling deeper visibility into their reliability.

Congratulations! You're now ready to configure your SLO and further enhance your service monitoring strategy within Nobl9.

related topics

• Services
• Service health dashboard