![]() Data Source: InfluxDB_pipeline_db, From: default, pipeline, WHERE: stage =~ /^$Stage$/, SELECT: field(duration), FORMAT AS: Time series and ALIAS BY: Duration. In the Metrics tab you now enter the following values. Add the Graph Panel here and select Edit in the title of panel. Now go to the still empty dashboard Pipeline. The prerequisite for this is that you have successfully completed the previous tutorials ( Part1, Part2, Part3). ![]() Steffen Lorenz Grafana, InfluxDB, Monitoring Create QA dashboards with Grafana (Part 4)įinally, we can create the first dashboard. I hope you have all the knowledge to create with Grafana awesome QA dashboards. On tab General have attentions to Repeat! The tab Legend for Graph panel have only Show checkbox enabled. 1x Graph panel and 1x Pie Chart panel ( we dynamically generate the others). Let’s get to the last dashboard ( Support). The Pie Chart Average: $Testers is simple, too. Here the important screens for Passed Total: $Testers:įor Singlestat Failed Total: $Testers, just change field(passed) to field(failed). Now you can edit the Singlestat panels ( one after the other). On tab Display enable only checkbox Lines. On tab Legend enable checkboxes Show, As Table, Min, Max and Current. On tab Metrics select Data Source InfluxDB_test_db and enter From: default suite WHERE: qa =~ /^$Testers$/, SELECT: field(passed) alias(Test Passed) field(skipped) alias(Tests Skipped) field(failed) alias(Tests Failed), FORMAT AS: Time series and ALIAS BY: $col.įor tab Axes just enable Show checkbox on Left Y and X-Axis, Unit: short, Scale: linear and Mode: Time. Under tab General enter for Title: Results: $Testers. 1x Graph panel, 2x Singlestat panel and 1x Pie Chart panel. ![]() I will just show now the most important configurations, from the 4th part you should already know the others.Īdd following panels. But after all, it’s up to your creativity how the results look. ![]() With a little Drag & Drop and resizing, your dashboard might look like this. Part 1, Part 2, Part 3 and Part 4 should have been successfully completed.įirst, I show the result. T=T00:39:42+0000 lvl=info msg="Request Completed" logger=context userId=2 orgId=1 uname=btai method=GET path=/api/datasources/proxy/1/api/v1/query_range status=502 remote_addr=127.0.0.1 time_ms=91 size=0 referer=" t=T00:39:42+0000 lvl=info msg="Request Completed" logger=context userId=2 orgId=1 uname=btai method=GET path=/api/datasources/proxy/1/api/v1/query_range status=502 remote_addr=127.0.0.1 time_ms=91 size=0 referer=" t=T00:39:42+0000 lvl=eror msg="Data proxy error" logger=data-proxy-log userId=2 orgId=1 uname=btai path=/api/datasources/proxy/1/api/v1/query_range remote_addr=127.0.0.1 referer=" error="http: proxy error: context canceled"ĭeployed: Please let me know if I should create a new issue as I know this one is closed.In the last tutorial of this series, we create the dashboards for testing and support. T=T00:39:42+0000 lvl=eror msg="Data proxy error" logger=data-proxy-log userId=2 orgId=1 uname=btai path=/api/datasources/proxy/1/api/v1/query_range remote_addr=127.0.0.1 referer=" error="http: proxy error: context canceled" Looking at the developer console, some web requests do not complete, get cancelled, or succeeds: Howering mouse over red triangles do not show anything useful:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |