Connect a data source

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

See how to connect a data source for your SLO

In Nobl9, data sources are the monitoring tools and solutions that provide the data used to calculate your SLOs. You can connect as many data sources as you need for flexible and comprehensive reliability tracking.

Nobl9 offers integration with several dozen monitoring solutions, ensuring seamless integration for accurate service reliability monitoring. For the most up-to-date list under the Integrations section of the Nobl9 application.

You can add your required data sources to your Nobl9 organization using either the agent or a direct method.

Want to know their difference?

Step-by-step

Follow these steps to add a data source on the Nobl9 Web:

1. Go to the Integrations > Sources.
2. Click .
3. Select the required data source from the list.
4. Provide your data source parameters.
5. Configure your data source in Nobl9—add the name, specify the required query delay and historical data retrieval parameters.

Each data source has its specific configuration. You can find the integration-specific details in the Sources section in the Nobl9 documentation.

Tips on naming and structuring

In Nobl9, add as many data sources as needed. This lets you monitor various system aspects with different sources, or use multiple instances of the same source with unique access levels and Nobl9 settings.

If you're unsure how to proceed, here are some examples of naming and structure to give you a clearer idea of how things could be organized:

Group your data sources

Group your data sources based on monitoring objectives.

For example, user behavior, system performance, latency tracking, resource usage, third-party dependencies, etc.

Standardize data source naming

Use a consistent naming convention to simplify identifying and managing your data sources.

Apply the naming structure like Solution name > Category > Monitoring target > Optional details.

For example, My data source > User flow > Redirects > Landing-to-registration > V2.

Maintain a mapping table to store key details about each data source

For example, your monitoring solution original name, the resource in your monitoring solution you defined for this data source, the monitored target, the responsible person details.

Leverage the description

For example, you can place your data source key details there.

Avoid generic or abbreviated names

For example, My data source > User registration is clearer than My data source or MyDSUR.

Amazing! Let's create a service for your SLO

related topics

• Release channels
• Data sources
• Data source troubleshooting