InfluxDB templates are preconfigured InfluxDB resources and can contain everything from dashboards and Telegraf configurations to notifications and alerts. Use InfluxDB templates to quickly get set up monitoring a specific technology, 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 by giving you resources that are already configured for your use-case.
- Facilitate secure, portable, and source-controlled InfluxDB resource states.
- Simplify sharing and using pre-built InfluxDB solutions.
A template consists of one or more files known as manifests that define the InfluxDB 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
should be included in the template, otherwise, the resources may not be usable.
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
Use InfluxDB stacks to manage InfluxDB templates. When you apply a template, InfluxDB associates resources in the template with a stack. Use stacks to add, update, or remove InfluxDB templates over time.
For more information, see InfluxDB stacks below.
Was this page helpful?
Thank you for your feedback!
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, use the following resources:
InfluxDB Cloud and InfluxDB Enterprise customers can contact InfluxData Support.