> For the complete documentation index, see [llms.txt](https://docs.ionos.com/cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ionos.com/cloud/observability/logging-service/dcd-how-tos/view-logging-pipelines.md).
# View Logging Pipelines
Once a logging pipeline is successfully created, the instance is listed on the **Logging Service** overview page.
To view the logging pipeline details, follow these steps:
1\. In the **DCD**, go to **Menu** > **Observability** > **Logging Service**.
{% hint style="success" %}
**Result:** A list of logging pipelines created is displayed. For every instance listed, you can view the following details:
* **NAME:** Displays the name of the logging pipeline. Select the name to view the respective pipeline details.
* **STATE:** Displays the state of the logging pipeline. Possible values are as follows:
* **Available:** The logging pipeline is available and in good condition.
* **Provisioning:** When the logging pipeline is either being updated or created.
* **Destroying:** When the logging pipeline is being deleted.
* **Failed:** When the logging pipeline creation or update has failed.
* **REGION:** Displays the region where the logging pipeline is created.
* **CREATION DATE:** Displays the date of creation of the logging pipeline.
* **LOG SOURCES:** Displays the number of log sources configured for the logging pipeline.
* **OPTIONS:** Select  to perform the following:
* **View & Edit:** You can view and edit the selected logging pipeline details.
* **Copy TCP endpoint:** Copy the TCP endpoint of the logging pipeline to use this endpoint in the log agent configuration, if applicable.
* **Copy HTTP endpoint:** Copy the HTTP endpoint of the logging pipeline to use this endpoint in the log agent configuration, if applicable.
* **Copy Grafana endpoint:** Copy the Grafana endpoint of the logging pipeline to use this endpoint in the Grafana instance for visualization and reporting purposes.
* **Copy Pipeline UUID:** Copy the UUID of the logging pipeline to use this identifier in the API calls.
* **Delete Pipeline:** Deletes the selected logging pipeline. In the dialog box that appears, select **Delete** to confirm deletion. For more information, see [Delete a Logging Pipeline](/cloud/observability/logging-service/dcd-how-tos/delete-logging-pipeline.md).
{% endhint %}
## View details of a selected Logging Pipeline
For the selected logging pipeline, you can view the following details:
* **Properties:** The following system information related to the logging pipeline is displayed:
* **Name:** Displays the name of the logging pipeline.
* **Region:** Displays the region of the logging pipeline.
* **Status:** Displays the state of the logging pipeline.
* **UUID:** The unique ID of the logging pipeline.
* **Creation date:** Specifies the date and time of logging pipeline creation.
* **Grafana Endpoint:** The Grafana endpoint URL for the logging pipeline, which is used to access the Grafana instance for visualization and reporting purposes.
* **TCP Endpoint:** The TCP endpoint of the logging pipeline, which is used to send logs from the log agent, if applicable.
* **HTTP Endpoint:** The HTTP endpoint of the logging pipeline, which is used to send logs from the log agent, if applicable.
* **Log sources:** Refers to the log sources defined for the logging pipeline. For more information, see [Define log sources](/cloud/observability/logging-service/dcd-how-tos/create-logging-service-pipeline.md#define-log-sources).
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.ionos.com/cloud/observability/logging-service/dcd-how-tos/view-logging-pipelines.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.