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
      • 📄Log Files
    • 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
      • 🩺SELinux
  • Support
    • How to Contact Us
  • GitHub Toolkit
Powered by GitBook
On this page
  • How Datasentinel Works
  • SELinux Status & Mode
  • Check
  • Modes
  • Quick test workflow
  • Requirement
  1. implementation
  2. Troubleshooting

SELinux

Security-Enhanced Linux (SELinux) is a Linux kernel security module that provides a mechanism for supporting access control security policies, including mandatory access controls (MAC).

Run all commands as root.

How Datasentinel Works

Datasentinel’s NGINX reverse-proxy talks to its internal services on a fixed set of local TCP ports:

  • 8216 — InfluxDB (times-series metrics store)

  • 9342 — PostgreSQL (configuration & metadata)

  • 12324 — Backend API

  • 13300 — Dispatcher (agent-less collection)

  • 7125 — Grafana (built-in dashboards)

NGINX config file: /etc/nginx/conf.d/datasentinel.conf

SELinux Status & Mode

Check

What you need
OS command
Expected output

Current runtime mode

getenforce

Enforcing, Permissive, or Disabled (If the command is missing, SELinux user-space tools aren’t installed.)

Detailed status

sestatus

Shows the loaded policy, runtime mode, and the mode that will apply on next boot.

Modes

  • Enforcing: SELinux actively blocks any action that violates the loaded security policy and logs the denial.

  • Permissive: SELinux allows actions that would normally be denied but still logs the violations for troubleshooting and policy tuning.

  • Disabled: SELinux is turned off entirely, so no security policy is loaded, and no access controls or audit logs are applied.

Quick test workflow

  1. Run getenforce to confirm the current mode.

  2. If you need to troubleshoot, switch to permissive (logs only):

    setenforce 0   # temporary—reverts at reboot
  3. Re-run getenforce; it should now read Permissive.

  4. When finished, return to enforcing:

    setenforce 1
  5. For a permanent change, edit /etc/selinux/config and reboot.

Requirement

SELinux Requirement For proper operation of all Datasentinel services, SELinux must be set to Permissive or Disabled on the host. Running in Enforcing mode can block critical internal traffic and file access, preventing components from starting or communicating.

Approach
What it does
Commands / Steps

1. Bypass SELinux

Turns SELinux off (or into permissive mode) so it never blocks Datasentinel.

• Temporary: setenforce 0  → mode switches to Permissive until next reboot. • Permanent: Edit /etc/selinux/config and set SELINUX=permissive or SELINUX=disabled, then reboot.

PreviousInfluxDBNextHow to Contact Us

Last updated 4 days ago

🩺