Add troubleshooting guide for timeseries with NaN
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 45/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- prometheus
- Domain
- documentation, observability
Research direction
Start with the Prometheus expressions and examples in the issue, then identify the repository documentation location for troubleshooting guidance. Document how instrumentation can avoid NaN values and how dashboard or alert exprs should handle potential NaNs; done means both cases are covered with clear examples.
Written by the indexing model from the issue text.
Description
Via @jameinel via matrix.
When timeseries have NaNs,
avg_over_time(
juju_apiserver_request_duration_seconds{
juju_controller="$controller",
juju_unit=~"$controller_host",
method="FullStatus",
quantile="0.99",error_code!~"not found|unauthorized access"
}[5m]
)
then aggregation operations produce unexpected results:
avg without (version, error_code)
(
juju_apiserver_request_duration_seconds{
juju_controller="$controller",
juju_unit=~"$controller_host",
method="FullStatus",
quantile="0.99",error_code!~"not found|unauthorized access"
}[5m]
)
and only when we filter out the NaNs with e.g.
avg(avg_over_time((juju_apiserver_request_duration_seconds > 0.0001)[1h:]))
then we get the expected results.
We should document:
- How to avoid
NaNs at instrumentation time. - Treating potential
NaNin dashboard/alertexprs.
- Dominant language
- HCL
- Stars
- 9
- Forks
- 12
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 11
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from canonical/observability-stack
-
Difficulty 1/5 Under an hour Newbie friendliness 85/100
canonical/observability-stack#476 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
canonical/observability-stack#428 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
canonical/observability-stack#422 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
canonical/observability-stack#344 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
canonical/observability-stack#306 ·
All issues in canonical/observability-stack
Similar issues
-
user-reported
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Kong/developer.konghq.com#7316 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
HarperFast/skills#96 ·
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
infinispan/infinispan#18150 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 78/100
fullcalendar/fullcalendar#8106 ·