Tracking SPA Navigation Latency with Dynatrace RUM Custom Actions
Learn how to use Dynatrace RUM’s custom JavaScript action API to measure SPA navigation latency, verify the results, and manage the trade‑offs of added overhead.
Loading…
ReadMeFeed / Community knowledge
Dynatrace
Real questions. Useful conversations. Find the people who know your stack.
Dynatrace
DevOps & observability · #dynatrace
Why Dynatrace's PurePath Changes How You Debug Microservice Latency
Dynatrace OneAgent's PurePath auto-instrumentation stitches requests across services without code changes. Here's how it helps debug latency, plus the overhead and coverage trade-offs.
Choosing Between OneAgent SDK and OpenTelemetry for Custom Metrics in Dynatrace
Deciding between OneAgent SDK and OpenTelemetry for custom metrics? Learn the trade-offs between native integration and vendor-neutrality to optimize your Dynatrace observability.
opentelemetrySolving the 'Invisible Dependency' Problem with Dynatrace Smartscape
Stop manually mapping microservices. Learn how Dynatrace OneAgent and Smartscape automate dependency discovery to eliminate visibility gaps and accelerate root-cause analysis.
How can Dynatrace dashboards handle date conversion across multiple regional time zones?
Managing observability across global infrastructure often requires aligning timestamps from different regional data centers. When creating visualizations in Dynatrace, there is a need to ensure that date and time data are converted accurately to a consistent reference zone, such as Coordinated Universal Time (UTC), without losing the original regional contex
UTC-aligned metric buckets vs client-side re-bucketing for local calendar day rollups
Context Dynatrace stores all metrics in UTC and computes aggregation buckets on UTC day boundaries. The web UI displays those buckets in the browser's local time zone, but the underlying bucket edges do not shift for daylight saving transitions. Automated consumers (API scripts, alerting pipelines, scheduled reports) must therefore decide whether to accept U
Adaptive Sampling Latency Spike in Dynatrace OneAgent 1.239 Under High Concurrency
Goal: Identify the concurrent request load at which Dynatrace OneAgent 1.239’s adaptive sampling mechanism begins to add measurable request latency, given that the effect is driven by thread‑contention detection and varies with host CPU capacity. Constraints: The adaptive sampling threshold is not exposed in the UI, its default value differs across environme
Dynatrace connection pool alerts: saturation threshold vs acquisition wait time for early exhaustion detection
Goal I want to configure Dynatrace metric events so my team is warned about intermittent connection pool exhaustion in our Java services before requests start failing, rather than after. OneAgent already reports pool usage for our HikariCP pools, and PurePath shows which requests hold connections. Constraints and uncertainty Alerting on absolute saturation (
Always-On PurePath vs Selective Filtering: Visibility Trade-off for Concurrent Latency
Latency that emerges only when multiple requests execute simultaneously is difficult to isolate in Dynatrace because the evidence required to expose lock contention, thread waits, or downstream serialization lives at the individual request level, while the initial symptom is usually visible only in aggregated service metrics. PurePath tracing provides that r