# Tags

These tags serve as attributes intricately linked with instances, providing a structured and organized means of categorization.

## How it Works

Certain tags are automatically generated, encompassing crucial details such as the server name, PostgreSQL version, instance name, and associated database (if applicable). 

Moreover, Datasentinel offers the flexibility to create additional tags, allowing for a comprehensive customization of instance attributes during the configuration phase. 

These user-defined tags can be tailored to align precisely with your specific needs and organizational requirements, enhancing the depth and accuracy of instance profiling within the system. 

{% hint style="info" %}
This comprehensive approach to tagging empowers users to efficiently classify and manage instances based on unique criteria, fostering a more refined and insightful understanding of their PostgreSQL environment.
{% endhint %}

Here is a list of possible tags that could be used:

* Special Tags
  * **pg\_instance**\
    \&#xNAN;*It is is a unique identifier in your environment, formed by concatenating the server name with **@**  and the connection name set during initialization.*
  * **server**
  * **pg\_version**\
    \&#xNAN;*Cluster version*
  * **database**
* Automated Tags generated through the active session sampling process on [pg\_stat\_activity](https://www.postgresql.org/docs/current/monitoring-stats.html#MONITORING-PG-STAT-ACTIVITY-VIEW)
  * **wait\_event\_type**
  * **wait\_event**
  * **application\_name**
  * **client\_host\_name**
  * **command\_type**
  * **query\_md5\_id**\
    Query identifier computed by Datasentinel
  * **user\_name**
* Custom Tags
  * **Can be any desired tag**

{% hint style="info" %}
Tags provide additional context and categorization to the data, allowing for more detailed analysis and insights.
{% endhint %}

## Blog Post

{% embed url="<https://www.datasentinel.io/blog/post/tags/>" %}

## Interactive Demo

This demo demonstrates how to use tags as filters within the User Interface.

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


---

# 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.datasentinel.io/manual/features/tips-and-hints/tags.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.