FROM SYMPTOM TO ROOT CAUSE
Observe, diagnose
and prove improvement.
TaranTuner connects host resources, database activity, session history, Wait Events and execution plans so teams can diagnose current incidents and reconstruct past slowdowns.
Investigate both current incidents and past performance degradation. TaranTuner brings together database operational expertise, including lock control, execution-plan analysis and automated reporting.
THREE GAPS, ONE FLOW
TaranTuner addresses four operational challenges.
Fragmented tools
Root-cause analysis often requires several tools: infrastructure monitoring for CPU, psql for sessions and separate logs for slow queries. Connecting symptoms to causes becomes a manual task.
- TaranTuner links server monitoring, database activity and SQL analysis through chart-range selection and contextual navigation.
Disconnected historical and live analysis
Historical analysis of what happened and real-time diagnosis of what is happening are separated across tools and screens, making past performance incidents especially difficult to trace.
- Analyze current Session Monitor activity and historical ASH workloads through the same SQL_ID and Wait Event perspectives.
Tuning without evidence
Improvements can remain subjective without numbers to prove results or trace later regressions. Recording each attempt manually is cumbersome.
- Continue from root-cause identification to improvement and verification with SQL Editor, execution plans, Advisor and Tuning Journal.
Repeated manual reporting
Database operating status and key performance metrics need regular reports, but gathering and documenting the data every time is labor-intensive.
- TaranTuner organizes the required operational metrics and automatically generates periodic reports instead of requiring repeated manual collection.
FLOW DIAGRAM
Detect the signal, narrow down the cause,
then act and report.
Restrict analytical access primarily to read-only SELECT queries. Permission models, audit logs, session safeguards and license host binding maintain strict operational control.
CAPABILITIES
From live observation to operational governance
REAL-TIME
Instances & Server Detail
Observe CPU, memory, disk, network and database KPIs in real time, then move from a selected chart interval to detailed analysis.
ANALYSIS
ASH & SQL Performance
Session samples at approximately three-second intervals and cumulative pg_stat_statements statistics reveal workload levels, Wait Classes and tuning priorities.
DBA TOOLS
Session Monitor & SQL Editor
Identify the root blocker with Lock Tree and distinguish Cancel from Terminate. Analyze execution plans through Tree, Grid, Advisor, Stats and Raw views.
INSIGHT
Database · Object · Log
Analyze database and object growth and efficiency while reviewing server logs, Live Log and Slow Query information together.
GOVERNANCE
RBAC & Audit Log
Support admin, dba, viewer and custom roles. Record logins, CRUD actions, settings, SQL execution and session actions in audit logs.
RELIABILITY
Alerts & Diagnostics
Detect anomalies with baseline and threshold rules. Self-check database, licensing, extensions, cache and authentication status.
ORACLE-TO-POSTGRESQL BRIDGE
Familiar performance concepts for the transition to PostgreSQL
FAMILIAR MODEL
SQL_ID · ASH · AWR · Wait Class
Map familiar Oracle performance-analysis concepts to PostgreSQL metrics so existing DBAs and tuning specialists can adapt quickly.
MEASURABLE CHANGE
Plan · Advisor · Journal
Explain problems using execution plans and measurements, and version each tuning attempt to make improvements reproducible.
TaranTuner reads only the information it needs without changing production database data. Limit access permissions and authorized servers, with usage records for safe management.
Live operations
Monitor instances, resources, sessions, locks and root blockers.
ASH & SQL
Use three-second session samples and cumulative SQL statistics to find workload drivers.
Tuning Journal
Record plan changes and Before/After metrics for every tuning attempt.