We currently have very few metrics related to Superset, as it does not expose metrics natively. However, we could/should collect the metrics exposed by gunicorn. That will give us an idea of the latency and % of successful metrics users experience.
Description
Description
Details
Details
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | brouberol | T353782 Decommission an-tool1010 | |||
| Resolved | brouberol | T347710 Migrate the Analytics Superset instances to our DSE Kubernetes cluster | |||
| Resolved | brouberol | T358778 Monitor the Superset Kubernetes application |
Event Timeline
Comment Actions
Change 1007642 had a related patch set uploaded (by Brouberol; author: Brouberol):
[operations/deployment-charts@master] superset: scrape gunicorn metrics
Comment Actions
Change 1007642 merged by Brouberol:
[operations/deployment-charts@master] superset: scrape gunicorn metrics
Comment Actions
Change 1007650 had a related patch set uploaded (by Brouberol; author: Brouberol):
[operations/deployment-charts@master] superset: fix, add missing gunicorn statsd export config
Comment Actions
Change 1007650 merged by Brouberol:
[operations/deployment-charts@master] superset: fix, add missing gunicorn statsd export config