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
  • Activation
  • Notification types
  • Email
  • Webhook
  • Custom Script
  1. Features
  2. Key Features
  3. Alerting

Settings

PreviousAlertingNextTemplates

Last updated 1 year ago

Activation

Alerting is turned off by default on the platform.

To activate this feature

  • Open tools menu

  • Click on Global settings

  • Then

You can opt for notifications regarding new problems and/or problem resolutions.

Notification types

You have the option to receive notifications in three different ways.

Problems persistently appear on the UI after creation, remaining visible even without an active notification.

Email

Webhook

A http POST request is sent to the specified url with a body containing the following fields

{
        "event_time": "2022-10-05 10:19:27",
        "notification_type": "PROBLEM",
        "pg_instance": "server@crm-production",
        "check_name": "memory_usage",
        "check_state": "CRITICAL",
        "message": "Memory usage: 95% used (1730MB/1835MB) [>=95% - CRITICAL]",
        "extra_data": {
            "value": 96,
            "used": 2512,
            "total": 3000
        }
}

The extra_data field can contain different fields depending on the check_name

Custom Script

The script must be executable and present on the platform server. It is executed at each notification and receive the following parameters:

  1. Event time

  2. Notification type

  3. PostgreSQL instance

  4. Check name

  5. State

  6. Message

Prior to email report delivery, configuring an is necessary.

A with a comprehensive toolkit that includes usage examples is accessible. The toolkit comes pre-installed on the on-premises platform and can be found at the following directory: /datasentinel/soft/datasentinel_toolkit.

🔔
SMTP server
GitHub repository
Alerting Settings