Send Metrics to the Platform

You can send metrics to the Monitoring Service using agents such as Fluent Bit, Grafana Agent, Prometheus, and OpenTelemetry Collector.

This Quickstart shows how to create a pipeline, get an API key, and configure one of these agents.

Prerequisites

  • An IONOS account with permissions to create monitoring pipelines.

  • Outbound HTTPS access on port 443.

  • The required agent or collector must be installed on your system.

Example endpoint:

123456789-metrics.987654321.monitoring.de-txl.ionos.com

Note: To make a final and complete address, add api/v1/push to the end of the endpoint. For example: 123456789-metrics.987654321.monitoring.de-txl.ionos.com/api/v1/push.

You can also find Prometheus configuration examples in our GitHub repository.

1

Create a pipeline

Send a POST request to the Monitoring Service API:

curl -X POST "https://monitoring.de-txl.ionos.com/pipelines"
  -H "Content-Type: application/json" \
  -d '{"name": "example-pipeline"}'

The response includes the httpEndpoint. Save this value.

2

API key usage

Use the API Key returned when you created the pipeline for authentication. You only need to generate a new one in specific cases, such as:

  • The key was accidentally shared

  • The key was lost

  • A team member with access left the company

To generate a new API key, run:

curl -X POST "https://monitoring.de-txl.ionos.com/pipelines/<PIPELINE_ID>/key"

This will issue a new API Key and replace the previous one.

The final endpoint for sending metrics is:

https://<HTTP_ENDPOINT>/api/v1/push

Configure an agent

Each agent requires the pipeline httpEndpoint and API key.

This example shows how to configure Fluent Bit to send metrics to the Monitoring Service.

  1. Install the Fluent Bit package for your distribution.

  2. Update the fluentbit.conf file with the HTTP endpoint and API key.

  3. Run Fluent Bit.

  4. Check the logs to confirm metrics are sent.

[OUTPUT]
    Name   http
    Match  *
    Host   <pipeline-endpoint-host>
    Port   443
    URI    /
    Header Authorization Bearer <apiKey>
    Format json

Troubleshooting

  1. Verify: Open the Monitoring Service dashboard and confirm that metrics appear.

  2. Invalid API key: Check that you copied the correct key.

  3. Connection errors: Verify outbound HTTPS access on port 443.

  4. No metrics displayed: Confirm that the agent is running and producing data.

Last updated

Was this helpful?