Skip to content
fernet.consultores

Splunk Observability Cloud

Database Monitoring.

The health and performance of your databases, and slow queries seen from the application's traces.

The problem we solve.

Many performance incidents end up in the database, but from the application they look like generic slowness. Without database metrics and without seeing which query each service is running, diagnosis drags on.

What’s included.

  • Database metric collection with the collector
  • Query performance seen from APM traces
  • Dashboards by database engine
  • Connection, lock and latency detectors
  • Correlation with the services that use them

How we work.

Five phases, always in the same order. Select each one to see what happens in it. In full projects they map onto the stages of our method.

We review what's monitored today, with which tools, which incidents went unnoticed and what it costs.

We design the collection layer with OpenTelemetry: agents, gateways, egress paths, common attributes and sampling.

We configure the receivers for each engine with a read-only user and link queries to APM traces.

We confirm that metrics arrive and that slow queries are traced to the service that issues them.

We tune cardinality, sampling and detectors based on real usage to contain cost and noise.

Technical capabilities.

  • OpenTelemetry receivers for PostgreSQL, MySQL, SQL Server and Oracle
  • Database Query Performance in Splunk APM
  • Connection and lock metrics
  • Detectors
  • Dashboards by engine

Use cases.

Slow queries

Know which query, from which service, is delaying responses.

Connection exhaustion

Detect full pools before the service goes down.

Capacity

Get ahead of database growth.

Benefits for your organisation.

  • Root cause pinpointed to the database
  • Less diagnosis time
  • Shared visibility between development and DBAs
  • Alerts with context

Deliverables.

  • Configured collectors
  • Dashboards by engine
  • Detectors
  • Operations guide

Frequently asked questions.

Which engines do you cover?

Those with an OpenTelemetry receiver, including PostgreSQL, MySQL, SQL Server and Oracle. We confirm your specific version in the assessment.

Is query data captured?

We configure what's logged so sensitive data isn't exposed.

Does anything need to be installed on the database server?

Usually a read-only user for the collector is enough.

Shall we talk about Database Monitoring?

Tell us about your situation. If this service is not what you need, we will tell you; if it is, we will propose a concrete first step.

Request this service