Documentation for automated readers
A curated documentation index is available at: https://grafana.com/llms.txt
A complete documentation index is available at: https://grafana.com/llms-full.txt
These indexes can help with page discovery before fetching individual documents.
This page is also available in Markdown, which may be easier for automated readers and AI tools to parse than HTML. The Markdown version is available at https://grafana.com/docs/grafana/v11.0/datasources/pyroscope/configure-pyroscope-data-source.md, or by sending Accept: text/markdown to https://grafana.com/docs/grafana/v11.0/datasources/pyroscope/configure-pyroscope-data-source/. For broader documentation discovery, the curated index is available at https://grafana.com/llms.txt and the complete index is available at https://grafana.com/llms-full.txt.
Important: This documentation is about an older version. It's relevant only to the release noted, many of the features and functions have been updated or replaced. Please view the current version.
Configure the Grafana Pyroscope data source
To configure basic settings for the data source, complete the following steps:
Click Connections in the left-side menu.
Under Your connections, click Data sources.
Enter
Grafana Pyroscopein the search bar.Click Grafana Pyroscope to display the Settings tab of the data source.
Set the data source’s basic configuration options:
Name Description NameA name to specify the data source in panels, queries, and Explore. DefaultThe default data source will be pre-selected for new panels. URLThe URL of the Grafana Pyroscope instance, for example, http://localhost:4100.Basic AuthEnable basic authentication to the data source. UserUser name for basic authentication. PasswordPassword for basic authentication. Minimal stepUsed for queries returning timeseries data. The Pyroscope backend, similar to Prometheus, scrapes profiles at certain intervals. To prevent querying at smaller interval, use Minimal step same or higher than your Pyroscope scrape interval. This prevents returning too many data points to the frontend.