Datasource

A datasource in Perses represents a connection configuration to an external system that provides observability data, such as metrics or traces. Datasources are there to allow retrieving data from different backends without hardcoding connection details everytime. They are thus reusable configuration objects that encapsulate how to query a specific data provider.

Datasources are implemented as plugins.

Supported backends

Perses supports multiple datasources & provides at least one option for each pillar of observability:

datasource

• ClickHouse
• Loki
• Prometheus
• Pyroscope
• Tempo
• VictoriaLogs

Configuring a datasource

Datasources in Perses can be configured at different scopes, providing flexibility for reuse and organization. More details about scopes at Datasource & Variable scopes.

Creating a datasource is usually done through the Perses UI, but you also have the option to rely on:

• Provisioning to have datasources directly available at startup – you should provision correct Datasource resources in this case.
• Datasource Discovery

A datasource can configured to be accessed directly, but you may want to get it proxied through the Perses backend for security reasons.