> For the complete documentation index, see [llms.txt](https://docs.datasentinel.io/manual/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.datasentinel.io/manual/features/tips-and-hints/simplified-pg_instance-display.md).

# Simplified pg\_instance Display

Created by Datasentinel, the pg\_instance tag is a unique identifier for your instance across the platform.

It's the concatenation of the server name or the fully qualified domain name (FQDN), followed by the **`@`** symbol, and ending with the instance name. (example: **`pg-cluster-01@crm_prod)`**<br>

{% hint style="info" %}
This tag is essential for quick identification of your database instances.
{% endhint %}

Sometimes, the FQDNs can be lengthy and cumbersome. They can clutter your user interface, making it challenging to quickly locate the information you need.

### **Customizable Display Options**

Starting from version 2024.01, you can effortlessly manage the display of the **`pg_instance`** tag using a newly introduced checkbox in the general dashboards.

<figure><img src="https://1072624949-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlcWi6G1jtNuyGT9C0pkc%2Fuploads%2FYeEXTQClDV6JXbNDUydu%2FFullInstanceIdentifier.png?alt=media&amp;token=3cb6b1f5-0321-4c8b-9867-faa45b8ac97a" alt=""><figcaption></figcaption></figure>

Choose to view:

* **The full pg\_instance name**
* **Only the Instance name**\
  A streamlined view for instances where the FQDN is known or less relevant, keeping your interface clean and focused.

{% hint style="info" %}
The Filter bar and dynamic Filter fields continue to be smoothly integrated with the `pg_instance` tag, ensuring efficient and streamlined navigation.
{% endhint %}

{% @arcade/embed url="<https://app.arcade.software/share/aqEXeJlhTtmSuAtDh6eI>" flowId="aqEXeJlhTtmSuAtDh6eI" %}


---

# 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.datasentinel.io/manual/features/tips-and-hints/simplified-pg_instance-display.md?ask=<question>&goal=<user_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.