public/grafana
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

[release-11.5.3] Rename Explore Apps to App Drilldown (#101259)

Browse Source 
Co-authored-by: Carl Bergquist <carl.bergquist@gmail.com>
Co-authored-by: Kim Nylander <104772500+knylander-grafana@users.noreply.github.com>
This commit is contained in:
Jack Baldry
2025-02-25 04:03:36 +02:00
committed by GitHub
co-authored by Carl Bergquist Kim Nylander
parent e79330dc08
commit 478ab85845
10 changed files with 68 additions and 60 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/sources/datasources/pyroscope/configure-pyroscope-data-source.md
+1 -1
View File
@@ -104,7 +104,7 @@ If you are running a self-managed Grafana instance or need to configure an addit
The connection URL for a self-managed Pyroscope backend depends on how Pyroscope is deployed.
Refer to the steps under [Query profiles in Grafana](https://grafana.com/docs/pyroscope/<PYROSCOPE_VERSION>/deploy-kubernetes/helm/#query-profiles-in-grafana) for more information on how to configure the data source.
If you plan to use the [Explore Profiles](ref:explore-profiles) application and you are running a self-managed Pyroscope backend in microservices mode, the data source connection URL should point to a gateway or proxy that routes requests to the corresponding Pyroscope service.
If you plan to use the [Profiles Drilldown](ref:explore-profiles) application and you are running a self-managed Pyroscope backend in microservices mode, the data source connection URL should point to a gateway or proxy that routes requests to the corresponding Pyroscope service.
Refer to the [Helm ingress configuration](https://github.com/grafana/pyroscope/blob/main/operations/pyroscope/helm/pyroscope/templates/ingress.yaml) for specific routing requirements.
## Authentication