Find data source plugins in the plugin catalog
Grafana annotations influxdb install#
You can add additional data sources as plugins, which you can install or create yourself. Grafana ships with several built-in data sources. This can be particularly useful when debugging data source queries using cURL. If a data source query request contains an X-Cache-Skip header, then Grafana skips the caching middleware, and does not search the cache for a response. In the data source list, click the data source that you want to clear the cache for.
If you are using Memcached, the system clears all data from the Memcached instance. Note: This action impacts all cache-enabled data sources. In the Edit Panel view, select the caching-enabled data source, expand the Query options, and enter your the TTL in milliseconds. This can be be useful when you have queries whose results change more or less often than the configured TTL. You can optionally override a data source’s configured TTL for individual dashboard panels. If you skip this step, then Grafana uses the default TTL.
(Optional) Choose custom TTLs for the data source’s queries and resources caching. 
In the data source list, click the data source that you want to turn on caching for. Under Your Connections, click Data sources. Click Connections in the left-side menu. To enable query caching for a single data source: For more information on Grafana roles and permissions, refer to About users and permissions.īy default, data source queries are not cached. You must be an Org admin or Grafana admin to enable query caching for a data source. See the developers page on plugin resources for details.į9df1f3051 (Docs: Plugins doc reorganization, part 1 (#69864)) Enable and configure query caching Note: Some data sources, such as Elasticsearch, Prometheus, and Loki, cache queries themselves, so Grafana query caching does not significantly improve performance. If caching is enabled in Grafana but the Caching tab is not visible for the given data source, then query caching is not available for that data source. To tell if a data source works with query caching, follow the instructions below to Enable and Configure query caching. More specifically, caching works with data sources that extend the DataSourceWithBackend class in the plugins SDK. Query caching also works for all data sources that include a backend. Some data sources, such as Elasticsearch, Prometheus, and Loki, cache queries themselves, so Grafana query caching does not improve performance. Query caching works for all Enterprise data sources as well as the following built-in data sources: Reduced likelihood that APIs will rate-limit or throttle requests.ĭata sources that work with query caching. 
Faster dashboard load times, especially for popular dashboards. You can make a panel retrieve fresh data more frequently by increasing the Max data points setting in the panel’s query options. In this example, cached data for this panel will be served for up to 10 minutes before Grafana queries the data source again and returns new data. For example, a full-width panel on a dashboard with a time range of last 7 days will retrieve fresh data every 10 minutes. Max data points are calculated based on the width of the panel. It is calculated like this: (max data points) / time range. Interval is visible in a panel’s query options. This means that wider panels and dashboards with shorter time ranges fetch new data more frequently than narrower panels and dashboards with longer time ranges. When a panel queries a cached data source, the time until this query fetches fresh data is determined by the panel’s interval. In production environments, a Redis or Memcached backend is highly recommended. Note: Storing cached queries in-memory can increase Grafana’s memory footprint.
0 kommentar(er)
