# FAQ

### What is a Logging Service?

The Logging Service platform provides a centralized and scalable solution for collecting, monitoring, and analyzing logs from your application and infrastructure. It utilizes specialized components to aggregate, parse, and store the logs seamlessly.

### What changed in the product during its transition from Early Access to General Availability?

The product contains enhancements that allow additional users under your contract number to create pipelines and log in to Grafana with their <code class="expression">space.vars.ionos\_cloud</code> credentials. Additionally, you can also enable group members to access and manage Logging Service by providing specific access rights to the group. For more information, see [<mark style="color:blue;">Set User Privileges for Logging Service</mark>](/cloud/observability/logging-service/dcd-how-tos/set-privileges-logging-service.md).

### What are the current limitations of Logging Service?

Logging Service has its own set of limitations. For more information, see [<mark style="color:blue;">Logging Service Limitations</mark>](/cloud/observability/logging-service/overview.md#limitations).

### How safe is my data if the same Logging Service platform is shared with multiple users?

Your data is secure and not shared with users using the same platform. The following defines the level of security provided by the platform:

* Each pipeline uses its unique endpoint to send logs to the log server over the Transport Layer Security (TLS).
* Each user has a separate partition because data is kept in different partitions.
* Each chunk of data within the partition is secured by server-side and client-side encryptions.

### Can I restrict the traffic sent to Logging Service endpoints?

Yes, we recommend configuring firewall rules using the authorized IP addresses associated with each endpoint to restrict the traffic to Logging Service endpoints. The following is a list of locations and their specific IP addresses:

| **Location** | **Region-specific Endpoints**      | **Link to IP addresses**                 |
| ------------ | ---------------------------------- | ---------------------------------------- |
| Berlin       | `https://logging.de-txl.ionos.com` | <https://logging.de-txl.ionos.com/ip/v4> |
| Logroño      | `https://logging.es-vit.ionos.com` | <https://logging.es-vit.ionos.com/ip/v4> |
| London       | `https://logging.gb-lhr.ionos.com` | <https://logging.gb-lhr.ionos.com/ip/v4> |
| Worcester    | `https://logging.gb-bhx.ionos.com` | <https://logging.gb-bhx.ionos.com/ip/v4> |
| Frankfurt    | `https://logging.de-fra.ionos.com` | <https://logging.de-fra.ionos.com/ip/v4> |
| Paris        | `https://logging.fr-par.ionos.com` | <https://logging.fr-par.ionos.com/ip/v4> |
| Lenexa       | `https://logging.us-mci.ionos.com` | <https://logging.us-mci.ionos.com/ip/v4> |
| Las Vegas    | `https://logging.us-las.ionos.com` | <https://logging.us-las.ionos.com/ip/v4> |
| Newark       | `https://logging.us-ewr.ionos.com` | <https://logging.us-ewr.ionos.com/ip/v4> |


---

# 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/logging-service/logging-service-faqs.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.