Closing the Observability Gap: Connecting Application Traces to Database Execution Plans
From the source: SolarWinds Blog08/24/26 The alert fires on p95 latency. A high-traffic API endpoint whose p95 normally sits under 100ms is now sitting at 380ms at the 95th percentile. That’s not right. You go through your initial checks. No errors. No recent deployments. No infrastructure alerts firing anywhere ... The post Closing the Observability Gap: Connecting Application Traces to Database Execution Plans appeared first…
Read the full story on SolarWinds BlogAsk the square
The story is what was announced. If it raises a question for your team, ask the people who run this technology day to day. Your post links back to this story, so the next reader finds it too.
Recent threads in Observability
Datadog vs Grafana stack vs OpenTelemetry + open source
If you have run more than one, compare them on cost at your scale, time to value and on-call experience.
How are you controlling observability costs without losing visibility?
Sampling, tiered retention, OpenTelemetry pipelines, switching vendors? What cut the bill the most?
Something wrong or out of date? Suggest a correction. We reply within 5 business days.
More from SolarWinds
Recent updates from SolarWinds, so you can tell whether this is a one-off or part of a pattern.
More in Observability
What other companies in Observability are doing. The category page shows who’s active, side by side.




