This guide provides insights into migrating runtime metrics to Grail, so you can smoothly transition to Latest Dynatrace.
Notebooks,
Dashboards, and other Dynatrace apps.
Notebooks or
Dashboards to test and validate your converted DQL queries.
Notebooks or
Dashboards.To convert a Classic runtime metric query:
Because there isn't an exact, one-to-one mapping between Classic metric selectors and DQL queries, some queries will require manual adjustments during the conversion.
The following tables list Classic technology runtime metric keys and their Grail equivalents, organized by mapping type. Select the section that matches your technology.
For more information about metric mapping, see New concepts.
Because Grail metrics are technology-specific, there's no direct relation between Metrics Classic and Grail metrics. You need to choose a technology-dedicated metric in Grail.
The following Classic metric selector and DQL query return equivalent results.
| Classic metric selector | DQL query |
|---|---|
|
|
The following Metrics Classic metrics for memory pool and garbage collection are JVM-based. You need to choose the relevant Java, Node.js, or .NET metric in Grail.
| Classic metric key | Grail metric keys |
|---|---|
builtin:tech.jvm.memory.gc.collectionTime | dt.runtime.jvm.gc.total_collection_timedt.runtime.clr.gc.collection_timedt.runtime.go.gc.collection_time |
builtin:tech.jvm.memory.pool.collectionTime | dt.runtime.jvm.gc.collection_timedt.runtime.nodejs.gc.collection_time |
builtin:tech.jvm.memory.gc.suspensionTime | dt.runtime.jvm.gc.suspension_timedt.runtime.clr.gc.suspension_timedt.runtime.go.gc.suspension_timedt.runtime.nodejs.gc.suspension_time |
The following Classic metrics for web servers hold values for different technologies. You need to choose the dedicated Apache, IIS, or NGINX metric in Grail.
| Classic metric key | Grail metric keys |
|---|---|
builtin:tech.webserver.connections.socketWaitingTime | dt.runtime.apache.connections.socket_waiting_timedt.runtime.iis.connections.socket_waiting_time |
builtin:tech.webserver.requests | dt.runtime.apache.requestsdt.runtime.iis.requestsdt.runtime.nginx.requests |
builtin:tech.webserver.threads.active | dt.runtime.apache.threads.activedt.runtime.iis.threads.active |
builtin:tech.webserver.threads.idle | dt.runtime.apache.threads.idledt.runtime.iis.threads.idle |
builtin:tech.webserver.threads.max | dt.runtime.apache.threads.maxdt.runtime.iis.threads.max |
builtin:tech.webserver.traffic | dt.runtime.apache.trafficdt.runtime.iis.trafficdt.runtime.nginx.traffic |
Some Grail metric keys contain values that were previously stored across multiple Classic metric keys. These are stored in Grail as dimensions.
The following Classic metric key and DQL query return equivalent results.
| Classic metric key | DQL query |
|---|---|
|
|
| Classic metric keys | Grail metric key | Filter by |
|---|---|---|
builtin:cloud.cloudfoundry.auctioneer.lprFailed (filtered by process type Go)builtin:cloud.cloudfoundry.auctioneer.lprStarted (filtered by process type Go) | dt.runtime.go.cf.auctioneer_lrp_auctions | filter:{status == "failed"}filter:{status == "started"} |
builtin:tech.go.http.badGatewaysbuiltin:tech.go.http.responses5xxbuiltin:tech.go.http.totalRequests | dt.runtime.go.http.requests | filter:{status == 502}filter:{status >= 500 and status <= 599} |
builtin:tech.go.memory.heap.idlebuiltin:tech.go.memory.heap.live | dt.runtime.go.memory.heap | filter:{state == "idle"}filter:{state == "live"} |
builtin:tech.go.scheduling.g.runningCountbuiltin:tech.go.scheduling.g.systemCount | dt.runtime.go.scheduler.goroutine_count | filter:{owner == "user"}filter:{owner == "system"} |
builtin:tech.go.scheduling.m.countbuiltin:tech.go.scheduling.m.idlingCountbuiltin:tech.go.scheduling.m.spinningCount | dt.runtime.go.scheduler.worker_thread_count | filter:{state == "Overall"}filter:{state == "Idling"}filter:{state == "Spinning"} |
builtin:tech.dotnet.gc.gen0Collectionsbuiltin:tech.dotnet.gc.gen1Collectionsbuiltin:tech.dotnet.gc.gen2Collections | dt.runtime.clr.gc.collection_count | filter:{generation == "Generation0"}filter:{generation == "Generation1"}filter:{generation == "Generation2"} |
builtin:tech.dotnet.memory.gen0Consumptionbuiltin:tech.dotnet.memory.gen1Consumptionbuiltin:tech.dotnet.memory.gen2Consumptionbuiltin:tech.dotnet.memory.LOHConsumption | dt.runtime.clr.memory.consumption | filter:{generation == "Generation0"}filter:{generation == "Generation1"}filter:{generation == "Generation2"}filter:{generation == "LargeObjectHeap"} |
builtin:tech.dotnet.threadpool.ioCompletionThreadsbuiltin:tech.dotnet.threadpool.workerThreads | dt.runtime.clr.threadpool.threads | filter:{type == "activeIOCompletionThreads"}filter:{type == "activeWorkerThreads"} |
The following Metrics Classic metrics don't have a dedicated Grail metric.
builtin:tech.nginx.cache.hitRatio
timeseriesmisses = sum(dt.runtime.nginx.plus.cache.misses),hits = sum(dt.runtime.nginx.plus.cache.hits)| fieldsAdd hit_ratio = misses[] / hits[]
builtin:tech.nginx.serverZones.active
builtin:tech.nginx.serverZones.inactive
builtin:tech.nodejs.uvLoop.count
builtin:tech.nodejs.uvLoop.loopLatency
builtin:tech.nodejs.uvLoop.processedLatency
builtin:tech.nodejs.uvLoop.totalTime