Scaleway's Cockpit allows you to monitor your applications and their infrastructure by giving you insights and context into their behavior. Cockpit also enables you to visualize your metrics, logs, and traces through a Grafana dashboard. With Cockpit, you can also push data from your Scaleway resources, if they are integrated with CockpitOpen in new context.
The Observability Cockpit provides you with two Prometheus Remote Write endpoints for pushing metrics and logs. You can push metrics with any Prometheus Remote Write compatible agent such as PrometheusOpen in new context, GrafanaOpen in new context or OpenTelemetry CollectorOpen in new context.
You can push logs with any Loki compatible agent such as PromtailOpen in new context, FluentdOpen in new context, Fluent BitOpen in new context, OpenTelemetry CollectorOpen in new context, or LogstashOpen in new context.
Refer to the Cockpit Global APIOpen in new context for information on how to perform Cockpit visualization actions such as retrieving your dashboard URLs, managing Grafana users, and synchronizing your data through Grafana dashboards.
(switchcolumn) (switchcolumn)
Concepts
Refer to our dedicated concepts pageOpen in new context to find definitions of the different terms referring to the Observability Cockpit.
(switchcolumn) (switchcolumn)
Quickstart
-
Configure your environment variables.
Note
This is an optional step that seeks to simplify your usage of the API.
Code -
Retrieve push URLs.
Retrieve your endpoints for metrics, logs, and traces from the Data sources tabOpen in new context of the Scaleway console. The
metrics_urlis a domain that exposes a Prometheus-like API to manage metrics, and thelogs_urlexposes a Loki API to manage logs.- The Prometheus Remote Write endpoint to push your metrics is the following:
https://xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx.metrics.cockpit.fr-par.scw.cloud/api/v1/push. - The Remote Write endpoint to push your logs is the following:
https://xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx.logs.cockpit.fr-par.scw.cloud/loki/api/v1/push - Traces have different endpoints depending on the push pathOpen in new context you use. The traces endpoint for the OpenTelemetry agent is:
https://xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx.traces.cockpit.fr-par.scw.cloud/otlp.
- The Prometheus Remote Write endpoint to push your metrics is the following:
-
Create your Cockpit token to push metrics, logs, and traces.
Find out how to create your Cockpit token via the consoleOpen in new context or run the following command to create it via the API.
CodeImportant
Your Cockpit token's
secret_keyonly displays once. Make sure that you save it. We strongly recommend that you only give the minimal amount of permissions to your token. -
Configure the Grafana alloy agent.
Find out how to configure the Grafana alloy agentOpen in new context to push your data to Cockpit.
-
Configure rules and alerts.
Upon creation, your Grafana instance is already configured by default with your logs and metrics data sources and with the alert manager data source. This means that you will be able to configure and manage advanced alerting rules, for metrics and logs, configure contact points and notification policies, from Grafana.
To do so, access your Grafana dashboardOpen in new context and read our dedicated documentationOpen in new context to find out how to configure alert rules for Scaleway resources. Refer to the External links section of this page if you are not familiar with the alert manager or alert rules.
Important
- Make sure that you select the
Scaleway Alertingalert manager, as Scaleway does not support theGrafanaalert manager.- Make sure that you create rules on the data source containing the data you wish to be alerted on rather than on Grafana. (
datasource-managed-alerts)
- Make sure that you create rules on the data source containing the data you wish to be alerted on rather than on Grafana. (
- Make sure that you select the
(switchcolumn)
Requirement
- You have a Scaleway accountOpen in new context
- You have created an API keyOpen in new context and that the API key has sufficient IAM permissionsOpen in new context to perform the actions described on this page
- You have installed
curlOpen in new context
(switchcolumn)
Technical information
Regional availability
Scaleway's infrastructure is spread across different regions. Your Cockpit resources are available in the Paris, Amsterdam and Warsaw regions (fr-par, nl-ams, pl-waw)
Current supported endpoints
Cockpit supports telemetry ingestion and querying using the following open-source technologies:
- MimirOpen in new context for metrics
- LokiOpen in new context for logs
- TempoOpen in new context for traces
- PrometheusOpen in new context for the alert manager
Cockpit exposes a subset of their HTTP APIs so users can push, query, and manage telemetry data from Cockpit.
Refer to the dedicated documentationOpen in new context to find out which API endpoints are supported by Cockpit for data source management.
Troubleshooting
Refer to our troubleshooting documentation if your pusher does not support HTTP headersOpen in new context or if no data showing up on Grafana dashboardsOpen in new context.
Technical limitations
- Metrics and logs data is retained 31 days. After this period, data older than 31 days is deleted.
- The number of active metrics time series is limited to 250,000 per Cockpit by default.
- The number of active log streams is limited to 5000 per Cockpit.
- It is not yet possible to downsample metrics.
Going further
For more information about Cockpit, you can check out the following pages:
- Cockpit DocumentationOpen in new context
- Scaleway Slack CommunityOpen in new context join the #observability-beta and the #observability channels
- Contact our support teamOpen in new context
External links
If you are interested in learning more, you can check out the following pages:
- Pushing logs using FluentbitOpen in new context. Fluentbit is another commonly used agent that collects and forwards logs.
- Pushing metrics using Prometheus's agent modeOpen in new context. Prometheus can be used in an "agent-mode" that can scrape local targets and forward them using remote-write. This is useful for scenarios where targets are exposed in a private network (like a VPN or a single host) but need to be forwarded outside of it.
- How to create a Mimir or Loki managed alerting rule using GrafanaOpen in new context.