# Metric Pipelines

A metric pipeline refers to an instance or configuration of the Monitoring Service you can create using the REST API. To create an instance of the Monitoring Service, you can request the designated regional endpoint based on your desired location:

* Berlin: `https://monitoring.de-txl.ionos.com/pipelines`
* Frankfurt: `https://monitoring.de-fra.ionos.com/pipelines`
* London: `https://monitoring.gb-lhr.ionos.com/pipelines`
* Worcester: `https://monitoring.gb-bhx.ionos.com/pipelines`
* Paris: `https://monitoring.fr-par.ionos.com/pipelines`
* Logroño: `https://monitoring.es-vit.ionos.com/pipelines`
* Lenexa: `https://monitoring.us-mci.ionos.com/pipelines`
* Las Vegas: `https://monitoring.us-las.ionos.com/pipelines`
* Newark: `https://monitoring.us-ewr.ionos.com/pipelines`

When creating a metric pipeline instance, you can define multiple metric streams within each pipeline. Each stream functions as a separate metric source, allowing you to organize and manage different sources of metrics within your monitoring system.

After the pipeline is set up, a unique endpoint is assigned to each pipeline, thus establishing a connection with an independent metric server. This endpoint serves as the designated destination for sending metrics generated by all the metric sources within the pipeline.

## Contract limitations

The maximum number of pipelines you are allowed to create. The default value is 10. If you require a higher limitation boundaries, you can contact [<mark style="color:blue;">IONOS CLOUD Support</mark>](https://docs.ionos.com/cloud/support/general-information/contact-information) team to discuss your specific requirements and adjust the limits accordingly.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.ionos.com/cloud/observability/monitoring-service/overview/metric-pipelines.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.