Incompatible with Builtin Prometheus Metrics?
See original GitHub issueHi there,
Love this extension - just wanted to check for clarification on how it is supposed to overlap with the builtin notebook prometheus metrics. I noticed when I install it, it takes over the metrics endpoint:
curl 'localhost:8888/metrics?token=...'
{"rss": 57704448, "limits": {}}
This seems to conflict with these metrics:
https://github.com/jupyter/notebook/blob/master/notebook/prometheus/metrics.py
Just wanted to check if this is expected or if I’m installing it wrong
Issue Analytics
- State:
- Created 3 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
"Drop Prometheus metrics with unsupported types" due to ...
After configuring prometheus I get Drop Prometheus metrics with unsupported types. Only Gauge, Counter and Summary are supported. and I'm ...
Read more >Prometheus metrics troubleshooting on Amazon EKS and ...
This section provides help for troubleshooting your Prometheus metrics setup on Amazon EKS and Kubernetes clusters.
Read more >5 Challenges with Prometheus Monitoring | Chronosphere
Learn the challenges of scaling with Prometheus monitoring. Including; increased need for management, reduced production, and slower diagnosis.
Read more >Troubleshooting Managed Service for Prometheus
This document describes some problems you might encounter when using Google Cloud Managed Service for Prometheus and provides information on diagnosing and ...
Read more >GitLab Prometheus metrics
Metric Type Since
gitlab_banzai_cached_render_real_duration_seconds Histogram 9.4
gitlab_cache_misses_total Counter 10.2
gitlab_cache_operation_duration_seconds Histogram 10.2
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I’m using 0.3.6 from PyPi and the /metrics endpoint is being used therefore clobbering the prometheus endpoint. Looking at the code it has indeed reverted back to /metrics. Are there plans to change this? Right now I have to choose between showing metrics to the developers or capturing metrics with prometheus whereas I would very much like to do both.
@colmaengus yes there will be a 0.4.0 release soon that should fix the clobbering: https://github.com/yuvipanda/nbresuse/pull/68