
* Use relative aliases for all non-current Grafana aliases Prevents non-latest documentation "stealing" the page away from latest and through permanent redirects for latest pages that no longer exist. The redirected pages are indexed by search engines but our robots.txt forbids them crawling the non-latest page. Signed-off-by: Jack Baldry <jack.baldry@grafana.com> * Remove aliases from shared pages Signed-off-by: Jack Baldry <jack.baldry@grafana.com> * Rewrite all current latest aliases to be next Signed-off-by: Jack Baldry <jack.baldry@grafana.com> * Fix typo in latest alias Signed-off-by: Jack Baldry <jack.baldry@grafana.com> * Remove all current page aliases find docs/sources -type f -name '*.md' -exec sed -z -i 's#\n *- /docs/grafana/next/[^\n]*\n#\n#' {} \; find docs/sources -type f -name '*.md' -exec sed -Ez -i 's#\n((aliases:\n *-)|aliases:\n)#\n\2#' {} \; Signed-off-by: Jack Baldry <jack.baldry@grafana.com> * Prettier Signed-off-by: Jack Baldry <jack.baldry@grafana.com> Signed-off-by: Jack Baldry <jack.baldry@grafana.com>
3.5 KiB
aliases | keywords | menuTitle | title | weight | ||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|
TestData DB | TestData DB data source | 1500 |
TestData DB data source
Grafana ships with a TestData DB data source, which creates simulated time series data for any [panel]({{< relref "../../panels-visualizations/" >}}). You can use it to build your own fake and random time series data and render it in any panel, which helps you verify dashboard functionality since you can safely and easily share the data.
For instructions on how to add a data source to Grafana, refer to the [administration documentation]({{< relref "../../administration/data-source-management/" >}}). Only users with the organization administrator role can add data sources.
Configure the data source
To access the data source configuration page:
- Hover the cursor over the Configuration (gear) icon.
- Select Data Sources.
- Select the TestData DB data source.
The data source doesn't provide any settings beyond the most basic options common to all data sources:
Name | Description |
---|---|
Name | Sets the name you use to refer to the data source in panels and queries. |
Default | Defines whether this data source is pre-selected for new panels. |
Create mock data
{{< figure src="/static/img/docs/v41/test_data_add.png" class="docs-image--no-shadow" caption="Adding test data" >}}
Once you've added the TestData DB data source, your Grafana instance's users can use it as a data source in any metric panel.
Choose a scenario
Instead of providing a query editor, the TestData DB data source helps you select a Scenario that generates simulated data for panels.
You can assign an Alias to each scenario, and many have their own options that appear when selected.
{{< figure src="/static/img/docs/v41/test_data_csv_example.png" class="docs-image--no-shadow" caption="Using CSV Metric Values" >}}
Available scenarios:
- Annotations
- Conditional Error
- CSV Content
- CSV File
- CSV Metric Values
- Datapoints Outside Range
- Exponential heatmap bucket data
- Grafana API
- Grafana Live
- Linear heatmap bucket data
- Load Apache Arrow Data
- Logs
- No Data Points
- Node Graph
- Predictable CSV Wave
- Predictable Pulse
- Random Walk
- Random Walk (with error)
- Random Walk Table
- Raw Frames
- Simulation
- Slow Query
- Streaming Client
- Table Static
- USA generated data
Import a pre-configured dashboard
TestData DB also provides an example dashboard.
To import the example dashboard:
- Navigate to the data source's [configuration page]({{< relref "#configure-the-data-source" >}}).
- Select the Dashboards tab.
- Select Import for the Simple Streaming Example dashboard.
To customize an imported dashboard:
To customize the imported dashboard, we recommend that you save it under a different name. If you don't, upgrading Grafana can overwrite the customized dashboard with the new version.
Use test data to report issues
If you report an issue on GitHub involving the use or rendering of time series data, we strongly recommend that you use this data source to replicate the issue. That makes it much easier for the developers to replicate and solve your issue.