You can install Promscale in several different ways. The method you choose depends on if your system is instrumented and collecting telemetry, or if you need to set these up.
Promscale does not, by default, provide instrumentation to collect telemetry from your applications and infrastructure. It is expected that you use Prometheus to collect metrics. You can also use OpenTelemetry to collect traces. When you have the instrumentation set up, you can use Promscale to ingest the metric and trace data.
search_path variable determines in what order schemas are searched and which objects such as tables, views, functions, and others do not require schema qualification to use. When you install Promscale, the Promscale extension modifies the
search_path of the database that it is connected to and adds its public schemas to the search path. This makes querying Promscale data easier. The public schemas that Promscale adds are:
If you have Prometheus or OpenTelemetry installed, you can install Promscale on these environments:
- Kubernetes: use Helm charts or a manifest file.
- Docker: use a pre-built Docker container.
- VM or bare metal: use the source file.
You can also use our prom-migrator tool to migrate your existing Prometheus data into Promscale.
If you have a Kubernetes environment, you can install a complete, pre-configured observability stack with Promscale. The observability stack (tobs) for Kubernetes includes Prometheus, OpenTelemetry, and Promscale.
Found an issue on this page?Report an issue!