Add grafana dashboards for initial build/provision upon component cre…#227
Conversation
rcerven
force-pushed
the
slo_dashboards
branch
2 times, most recently
from
bef455e to
24b671d
Compare
Signed-off-by: Robert Cerven <rcerven@redhat.com>
rcerven
force-pushed
the
slo_dashboards
branch
from
24b671d to
680fea4
Compare
…ation, simple builds, PaC provisions and unprovisions and triggers STONEBLD-1773 STONEBLD-1774 Signed-off-by: Robert Cerven <rcerven@redhat.com>
rcerven
force-pushed
the
slo_dashboards
branch
from
680fea4 to
7ddcaa4
Compare
|
|
/retest |
|
How should we review this? Which parts of the generated config are relevant? Or how could we deploy it and view it ourselves? |
in diff you can see that it shows 1 file as moved and changed (so there you can see actual changes I've made basically for all of them), so I've used "template" from existing dashboards and changed just metric name & those descriptions |
That helps 👍 So all the dashboards are pretty much copy-pastes of each other, just for different metrics? Still though, if I wanted to deploy it and check it on my cluster, how would I do it? I probably know how to deploy it at least (https://redhat-appstudio.github.io/infra-deployments/docs/development/deployment.html#deploying-your-versions-of-crds) but not sure where to see the dashboard |
|
in the cluster find namespace : appstudio-grafana there check route, and there is url to grafana and there you can see dashboards |
| { | ||
| "editorMode": "builder", | ||
| "exemplar": false, | ||
| "expr": "redhat_appstudio_buildservice_simple_build_pipeline_creation_time_count", |
There was a problem hiding this comment.
So for this example, metric simple_build_pipeline_creation_time is exported from build-service controller, and does redhat_appstudio_buildservice_simple_build_pipeline_creation_time_count map to that metric?
Does its format follow some Grafana or Promethues expression spec?
Is part redhat_appstudio_buildservice_ fixed and defined for build-service specifically?
Does part _count show the calculation on the collected data of the metric?
There was a problem hiding this comment.
"Does its format follow some Grafana or Promethues expression spec?"
not sure what you mean, I don't know much about grafana of prometheus
but in the cluster our metric : simple_build_pipeline_creation_time
has to be queried as : redhat_appstudio_buildservice_simple_build_pipeline_creation_time
_count calculates number of metrics
_sum does sum for them
those are prometheus/grafana thingies
|
/test build-service-e2e |
|
@rcerven: The following test failed, say
Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
|
Deployed on my cluster. The dashboards are shown, however after submitting a few builds, both simple and PaC builds, number is still 0 in the dashboard by waiting for a while after the submission. "No data" is shown inside initial build dashboard. Any additional configuration should be done after bootstrapping the cluster? |
I have no idea I was testing those metrics which we are sending to prometheus in dev cluster and those extended names worked not sure what has to be done for dashboards |
4 participants
…ation, simple builds, PaC provisions and unprovisions and triggers
STONEBLD-1773
STONEBLD-1774