Datasentinel Docs
Visit our websiteBlogRelease Notes
  • 👋Welcome
  • 🆓Free Trial
  • 📣Release Notes
  • Getting started
    • Architecture
    • Installation
      • 🌐Platform
      • 🕶️Agent
    • PostgreSQL clusters
      • 🔌Extensions
        • 🔌pg_stat_statements
        • 🔌pg_store_plans
        • 🔌system_stats
        • 🔌pg_buffercache
      • 🕶️Monitoring User
      • ➕Adding Connection
    • FAQs
      • ❓Platform FAQ
      • ❓Agent FAQ
  • Features
    • Key Features
      • 📊Session History
      • 📊Top Queries
      • 📂Top Tables
      • 🔓Lock Explorer
      • 📈Cluster & System Metrics
      • ⌚Live360
      • 📰Reporting
      • 🔔Alerting
        • Settings
        • Templates
        • Silences
        • Manager
    • Other Features
      • 📡Agentless Monitoring
      • 🛡️Role Based Access
      • 🔂Changed Parameters
    • Tips & Hints
      • 🖥️User Interface
      • 🏷️Tags
      • 🔀Metric Correlation
      • 👁️‍🗨️Consolidated View
      • ❗Graphical Annotations
      • ☁️Predefined Providers
      • ❓Wait Event Description
      • ®️Read Replicas
      • 👁️‍🗨️Agentless & System Metrics
      • ☑️Simplified pg_instance Display
  • implementation
    • Platform Usage
      • ⚙️Configuration
        • 🔑License
        • 📓LDAP
        • ✉️SMTP
        • 📋Audit
        • 👨‍🏭Users & Roles
      • 🧩API
        • 🔗Access Token
        • 🧩Connection API
        • 🧩Role API
        • 🧩User API
        • 🧩Reporting API
        • 🧩Workload API
        • 🧩Alerting API
      • 🛠️Tooling
    • Agent Usage
      • 📣Release Notes
      • ⌨️CLI
      • 🧩API
      • 🗃️Collection Level
      • 🔬Internals
    • Upgrade
      • 🔄Platform
      • 🔄Agent
    • Troubleshooting
      • 🩺Error message: “502 Bad Gateway”
      • 🩺The UI is not displaying any metrics for my new instance.
      • 🩺UI dashboard is encountering loading errors
      • 🩺InfluxDB
  • Support
    • How to Contact Us
  • GitHub Toolkit
Powered by GitBook
On this page
  • How it Works
  • Blog Post
  • Interactive Demo
  1. Features
  2. Tips & Hints

Tags

A tag is comprised of both a key and a corresponding value, working together to represent a distinct property.

PreviousUser InterfaceNextMetric Correlation

Last updated 1 year ago

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.

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.

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

  • Special Tags

    • pg_instance 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 Cluster version

    • database

  • Automated Tags generated through the active session sampling process on

    • 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

Tags provide additional context and categorization to the data, allowing for more detailed analysis and insights.

Blog Post

Interactive Demo

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

🏷️
pg_stat_activity
LogoHow to use TAGs efficiently with Datasentinel