Feature · /configuration
コンフィギュレーション
Postgresチューニングの都市伝説は終了 — 実際のワークロードを把握した推奨。
In one line
パラメーターインベントリ、ドリフト検出、ワークロード対応の推奨。
What you get
- Snapshot of every Postgres GUC / MySQL system variable / Mongo config / Oracle init.ora
- Drift detection: 'this host has effective_cache_size = 4GB but every other host has 16GB'
- Workload-aware recommendations (powered by the AI engine)
- Change attribution where the database supports it (pg_settings 'sourcefile' + 'sourceline')
- Compliance-style reporting (CIS Postgres benchmark, AWS RDS recommendations)
FAQ
Can recommendations be auto-applied?+
No — recommendations are advisory only. Obsfly never writes to a customer database.
Related reading
MySQL
MySQL Performance Schema vs sys schema: a 2026 monitoring guide
Performance Schema is unreadable. sys schema is friendly but lossy. Here's exactly which to use for which production question, with the eight queries every MySQL DBA should know by heart.
MongoDB
MongoDB performance monitoring in production: a 2026 guide
Four surfaces (serverStatus, db.stats, currentOp, profiler), a sane default for what to scrape from each, and how to reason about replica lag, oplog window, and aggregation pipeline cost.
Postgres
Postgres slow queries: 12 causes and how to find each one
A field-tested playbook for diagnosing a slow Postgres query in production — from missing indexes to plan flips to bloated tables — with the SQL to find each cause and the fix.