InfluxDB templates are prepackaged InfluxDB configurations that contain everything from dashboards and Telegraf configurations to notifications and alerts. Use InfluxDB templates to quickly set up a fresh instance of InfluxDB, back up your dashboard configuration, or share your configuration with the InfluxData community.
InfluxDB templates do the following:
- Reduce setup time
- Facilitate secure, portable, source-controlled InfluxDB platform states.
- Simplify sharing and using pre-built InfluxDB solutions.
A template consists of a single file known as a manifest that defines the InfluxDB state and associated resources. Template manifests support the following formats:
Template manifests are compatible with Kubernetes Custom Resource Definitions (CRD).
metadata.name field in manifests uniquely identifies each resource in the template.
metadata.name values must be DNS-1123 compliant.
If resources in the template depend on other InfluxDB resources, all dependencies
must be included in the template.
See Create an InfluxDB template for information about generating template manifests.
Include the following resources in a template:
- dashboard variables
- notification endpoints
- notification rules
- Telegraf configurations
InfluxDB stacks are stateful InfluxDB templates. When you apply a template, InfluxDB associates resources in the template with a stack. Use stacks to add, update, or remove templated resources over time.
For more information, see InfluxDB Stacks below.
Support and feedback
Thank you for being part of our community! We welcome and encourage your feedback and bug reports for InfluxDB and this documentation. To find support or submit feedback, the following resources are available:
- Post in the InfluxData Community.
- Submit documentation issues to the InfluxDB 2.0 documentation repository.
- Submit InfluxDB issues to the InfluxDB repository.
For our InfluxDB Cloud customers, InfluxData Support is also available.