Grafana annotations influxdb1/2/2024 ![]() ![]() Here, we actually have two different product flavors: one for server/datacenter and another cloud based. The first step is to extract data from Xray. As a consequence, I came with something like this: Xray > InfluxDB > Grafana. So, as this initial approach was unsuccessful, I tried to depict what would be the proper architecture for this. These are just a few I won't cover the configuration of these or explore this further to not make this article too exhaustive. overload of API request, as data needs to be fetched each time it is needed.unable to deal with pagination of the underlying APIs.It's possible to do so using some Grafana plugins (GraphQL, JSON API, Infinity) but we will face many limitations, including: I started by trying to use Grafana directly to import the test runs from the source application (i.e., Xray), using either the GraphQL API, for Xray cloud, or the REST API, for Xray server/DC. Grafana is a platform used to analyze and visualize data, supporting multiple sources, dashboard customization, plugins, and more. It also provides integration with Grafana among other. It can be used to store and query our time-related data: in this case our test runs. In this case, there's an endpoint that we can use to export the test runs from. The Xray server/datacenter product provides a REST API only, for the time being. The latter is more powerfull and that's the one we can use to extract the test runs. Xray cloud (i.e., for Jira cloud) provides a REST API and a GraphQL API. Xray is a well-known test management solution that works highly integrated with Jira (it needs it, actually). In this rather long detailed article, we'll also cover InfluxDB and how it can be useful to store time series data. Well, it was time hope this helps you out and inspires you to try some of these tools. I've met Grafana in the past but never implemented an end-to-end scenario with it. The idea was to use Grafana to analyze and visualize test results, in this case from a well-known test management solution, Xray, where I work btw. ![]() 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.After doing a similar exercise with Splunk, I decided to give a try to Grafana along with InfluxDB. 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 |