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
  • Configuration Files
  • Logs
  • Internal Limits
  • Memory usage
  1. implementation
  2. Agent Usage

Internals

Configuration Files


The agent stores its configuration on the hidden directory .datasentinel located in the user’s home directory.

2 files are present:

  • agent.yml

  • connections.yml

You can modify the agent properties directly through these files (except for passwords, which are encrypted).

Logs


The agent’s actions are recorded in the datasentinel.log file located in the log subdirectory of its distribution.

The log file is automatically rotated to remove outdated entries and manage data retention.

By default, the log level is set to INFO. To increase the log level, one can set it to debug in the agent section of the configuration file agent.yml.

Internal Limits


The agent has limits in place to control its consumption and prevent excessive overhead.

Memory usage

Memory consumption of the agent is checked every 15 minutes. If it exceeds the defined limit (2 gigabytes by default) for any reason (which should never append) , the agent stops and notifies the platform of its shutdown. A line is also added to its log file.

You can control this memory limit by setting the max-memory-mb parameter in the agent’s configuration file and restarting the agent for the changes to take effect.

{
  "version": "3.2.0",
  "port": 8282,
  "max-memory-mb": 1024,
  "last_upload": "",
  "collection-rate": "high",
  "tables-monitoring-limit": 3000,
  "query-monitoring-limit": 30000,
  "sql-max-size": 312000,
  "start_time": "2020-10-23 15:43:23",
  "proxy": {
    "host": "",
    "port": 0,
    "user": "",
    "password": ""
  },
  "upload_server": {
    "host": "51.158.105.50",
    "port": 443
  },
  "connections": {
    "connections": 1,
    "running": 1,
    "not running": 0
  }
}
PreviousCollection LevelNextUpgrade

Last updated 1 year ago

🔬