IntenseWebs/grafana
3
0
Fork 0
mirror of https://github.com/grafana/grafana.git synced 2025-01-11 00:22:06 -06:00
Code Issues Packages Projects Releases Wiki Activity

docs: what's new, add traces and k6 integration (#75401)

Browse Source 
* docs: what's new, add traces and k6 integration

* Add exception for Heitor's name

Signed-off-by: Jack Baldry <jack.baldry@grafana.com>

* Update index.md

Wei Li feedback

* docs: remove on-prem comment

* docs: add a couple options

* docs: update k6 whats new update

* Apply suggestions from code review

Co-authored-by: Isabel <76437239+imatwawana@users.noreply.github.com>

* docs: update based on feedback

---------

Signed-off-by: Jack Baldry <jack.baldry@grafana.com>
Co-authored-by: Jack Baldry <jack.baldry@grafana.com>
Co-authored-by: Isabel <76437239+imatwawana@users.noreply.github.com>
This commit is contained in:
Heitor Tashiro Sergent 2023-10-04 11:04:48 -05:00 committed by GitHub
parent 13a10b9bf0
commit 1b4c2fc948
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 19 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
.codespellignore
View File

@ -2,4 +2,5 @@ aks
eror
iam
wan
[Operato Windrose](https://grafana.com/grafana/plugins/operato-windrose-panel/)
[Operato Windrose](https://grafana.com/grafana/plugins/operato-windrose-panel/)
sergent

17
docs/sources/whatsnew/whats-new-next/index.md
View File

@ -18,6 +18,23 @@ weight: -37
Welcome to Grafana Cloud! Read on to learn about the newest changes to Grafana Cloud.
## Distributed tracing in Grafana Cloud k6
<!-- Heitor Tashiro Sergent -->
_Generally available in Grafana Cloud_
You can now use the Grafana Cloud Traces integration with Grafana Cloud k6 to quickly debug failed performance tests and proactively improve application reliability.
Distributed tracing in Grafana Cloud k6 only requires two things:
- An application instrumented for tracing with Grafana Cloud Traces.
- Adding a few lines of code to your existing k6 scripts.
The integration works by having k6 inject tracing metadata into the requests it sends to your backend services when you run a test. The tracing data is then correlated with k6 test run data, so you can understand how your services and operations behaved during the whole test run. The collected tracing data is aggregated to generate real-time metrics—such as frequency of calls, error rates, and percentile latencies—that can help you narrow your search space and quickly spot anomalies.
To learn more, refer to the [Integration with Grafana Cloud Traces documentation](/docs/grafana-cloud/k6/analyze-results/integration-with-grafana-cloud-traces/) and [Distributed Tracing in Grafana Cloud k6 blog post](https://grafana.com/blog/2023/09/19/troubleshoot-failed-performance-tests-faster-with-distributed-tracing-in-grafana-cloud-k6/).
## Tenant database instance name and number for SAP HANA® data source
<!-- Miguel Palau -->