(Legacy) Heuristic and Deprecated Metrics
Various network-related metrics reported by Sysdig, including response times, are calculated at the kernel level by measuring latency between systems calls. In an effort to ensure Sysdig remains the trusted source of infrastructure insights, moving forward we will be labeling some network related metrics as heuristic and are tagging with the symbol in the application.
Existing alerts using these metrics will not be modified or disabled. However, these alerts will not be able to be updated.
Additional heuristic metric details are listed below:
|Metric||Set New Alerts|
Based on low usage patterns, Sysdig has decided to deprecate the following metrics on August 1, 2018. Users will continue to have the ability to collect similar data using Prometheus, or another method of code instrumentation (i.e. StatsD or JMX for Java applications).
The table below shows the current metrics and options for similar functionality.
|Current Metric||Alternative Starting August 1, 2018|
|capacity.estimated.request.stolen.count||Create your application metrics using Prometheus, StatsD or JMX for Java applications.|
|net.sql.request.time.worst||Max aggregation (net.sql.request.time)|
|net.mongodb.request.time.worst||Max aggregation (net.mongodb.request.time)|
|net.http.request.time.worst||Max aggregation (net.http.request.time)|
Was this page helpful?
Glad to hear it! Please tell us how we can improve.
Sorry to hear that. Please tell us how we can improve.