All Integrations / OpenStack and TimescaleDB Integration

OpenStack and TimescaleDB Integration

Powerful performance with an easy integration, powered by Telegraf, the open source data connector built by InfluxData.

Get This Integration for Free
info

This is not the recommended configuration for real-time query at scale. For query and compression optimization, high-speed ingest, and high availability, you may want to consider <a href="/integrations/openstack-influxdb/">OpenStack and InfluxDB</a>.

5B+

Telegraf downloads

#1

Time series database
Source: DB Engines

1B+

Downloads of InfluxDB

2,800+

Contributors

Table of Contents

Useful Links

Documentation

Telegraf Quickstart Training

Infrastructure Monitoring with Telegraf

Powerful Performance, Limitless Scale

Collect, organize, and act on massive volumes of high-velocity data. Any data is more valuable when you think of it as time series data. with InfluxDB, the #1 time series platform built to scale with Telegraf.

See Ways to Get Started

Input and output integration overview

<p>This plugin collects metrics from essential OpenStack services, facilitating the monitoring and management of cloud infrastructures.</p>

<p>This output plugin delivers a reliable and efficient mechanism for routing Telegraf collected metrics directly into TimescaleDB. By leveraging PostgreSQL’s robust ecosystem combined with TimescaleDB’s time series optimizations, it supports high-performance data ingestion and advanced querying capabilities.</p>

Integration details

OpenStack

<p>The OpenStack plugin allows users to collect performance metrics from various OpenStack services such as CINDER, GLANCE, HEAT, KEYSTONE, NEUTRON, and NOVA. It supports multiple OpenStack APIs to fetch critical metrics related to these services, enabling comprehensive monitoring and management of cloud resources. As organizations increasingly adopt OpenStack for their cloud infrastructure, this plugin plays a vital role in providing insights into resource usage, availability, and performance across the cloud environment. Configuration options allow for customized polling intervals and filtering unwanted tags to optimize performance and cardinals.</p>

TimescaleDB

<p>TimescaleDB is an open source time series database built as an extension to PostgreSQL, designed to handle large scale, time-oriented data efficiently. Launched in 2017, TimescaleDB emerged in response to the growing need for a robust, scalable solution that could manage vast volumes of data with high insert rates and complex queries. By leveraging PostgreSQL’s familiar SQL interface and enhancing it with specialized time series capabilities, TimescaleDB quickly gained popularity among developers looking to integrate time series functionality into existing relational databases. Its hybrid approach allows users to benefit from PostgreSQL’s flexibility, reliability, and ecosystem while providing optimized performance for time series data.</p> <p>The database is particularly effective in environments that demand fast ingestion of data points combined with sophisticated analytical queries over historical periods. TimescaleDB has a number of innovative features like hypertables which transparently partition data into manageable chunks and built-in continuous aggregation. These allow for significantly improved query speed and resource efficiency.</p>

Configuration

OpenStack

<pre><code class="language-toml">[[inputs.openstack]] ## The recommended interval to poll is '30m' ## The identity endpoint to authenticate against and get the service catalog from. authentication_endpoint = "https://my.openstack.cloud:5000" ## The domain to authenticate against when using a V3 identity endpoint. # domain = "default" ## The project to authenticate as. # project = "admin" ## User authentication credentials. Must have admin rights. username = "admin" password = "password" ## Available services are: ## "agents", "aggregates", "cinder_services", "flavors", "hypervisors", ## "networks", "nova_services", "ports", "projects", "servers", ## "serverdiagnostics", "services", "stacks", "storage_pools", "subnets", ## "volumes" # enabled_services = ["services", "projects", "hypervisors", "flavors", "networks", "volumes"] ## Query all instances of all tenants for the volumes and server services ## NOTE: Usually this is only permitted for administrators! # query_all_tenants = true ## output secrets (such as adminPass(for server) and UserID(for volume)). # output_secrets = false ## Amount of time allowed to complete the HTTP(s) request. # timeout = "5s" ## HTTP Proxy support # http_proxy_url = "" ## Optional TLS Config # tls_ca = /path/to/cafile # tls_cert = /path/to/certfile # tls_key = /path/to/keyfile ## Use TLS but skip chain &amp; host verification # insecure_skip_verify = false ## Options for tags received from Openstack # tag_prefix = "openstack_tag_" # tag_value = "true" ## Timestamp format for timestamp data received from Openstack. ## If false format is unix nanoseconds. # human_readable_timestamps = false ## Measure Openstack call duration # measure_openstack_requests = false </code></pre>

TimescaleDB

<pre><code class="language-toml"># Publishes metrics to a TimescaleDB database [[outputs.postgresql]] ## Specify connection address via the standard libpq connection string: ## host=... user=... password=... sslmode=... dbname=... ## Or a URL: ## postgres://[user[:password]]@localhost[/dbname]?sslmode=[disable|verify-ca|verify-full] ## See https://www.postgresql.org/docs/current/libpq-connect.html#LIBPQ-CONNSTRING ## ## All connection parameters are optional. Environment vars are also supported. ## e.g. PGPASSWORD, PGHOST, PGUSER, PGDATABASE ## All supported vars can be found here: ## https://www.postgresql.org/docs/current/libpq-envars.html ## ## Non-standard parameters: ## pool_max_conns (default: 1) - Maximum size of connection pool for parallel (per-batch per-table) inserts. ## pool_min_conns (default: 0) - Minimum size of connection pool. ## pool_max_conn_lifetime (default: 0s) - Maximum connection age before closing. ## pool_max_conn_idle_time (default: 0s) - Maximum idle time of a connection before closing. ## pool_health_check_period (default: 0s) - Duration between health checks on idle connections. # connection = "" ## Postgres schema to use. # schema = "public" ## Store tags as foreign keys in the metrics table. Default is false. # tags_as_foreign_keys = false ## Suffix to append to table name (measurement name) for the foreign tag table. # tag_table_suffix = "_tag" ## Deny inserting metrics if the foreign tag can't be inserted. # foreign_tag_constraint = false ## Store all tags as a JSONB object in a single 'tags' column. # tags_as_jsonb = false ## Store all fields as a JSONB object in a single 'fields' column. # fields_as_jsonb = false ## Name of the timestamp column ## NOTE: Some tools (e.g. Grafana) require the default name so be careful! # timestamp_column_name = "time" ## Type of the timestamp column ## Currently, "timestamp without time zone" and "timestamp with time zone" ## are supported # timestamp_column_type = "timestamp without time zone" ## Templated statements to execute when creating a new table. # create_templates = [ # '''CREATE TABLE {{ .table }} ({{ .columns }})''', # ] ## Templated statements to execute when adding columns to a table. ## Set to an empty list to disable. Points containing tags for which there is ## no column will be skipped. Points containing fields for which there is no ## column will have the field omitted. # add_column_templates = [ # '''ALTER TABLE {{ .table }} ADD COLUMN IF NOT EXISTS {{ .columns|join ", ADD COLUMN IF NOT EXISTS " }}''', # ] ## Templated statements to execute when creating a new tag table. # tag_table_create_templates = [ # '''CREATE TABLE {{ .table }} ({{ .columns }}, PRIMARY KEY (tag_id))''', # ] ## Templated statements to execute when adding columns to a tag table. ## Set to an empty list to disable. Points containing tags for which there is ## no column will be skipped. # tag_table_add_column_templates = [ # '''ALTER TABLE {{ .table }} ADD COLUMN IF NOT EXISTS {{ .columns|join ", ADD COLUMN IF NOT EXISTS " }}''', # ] ## The postgres data type to use for storing unsigned 64-bit integer values ## (Postgres does not have a native unsigned 64-bit integer type). ## The value can be one of: ## numeric - Uses the PostgreSQL "numeric" data type. ## uint8 - Requires pguint extension (https://github.com/petere/pguint) # uint64_type = "numeric" ## When using pool_max_conns &gt; 1, and a temporary error occurs, the query is ## retried with an incremental backoff. This controls the maximum duration. # retry_max_backoff = "15s" ## Approximate number of tag IDs to store in in-memory cache (when using ## tags_as_foreign_keys). This is an optimization to skip inserting known ## tag IDs. Each entry consumes approximately 34 bytes of memory. # tag_cache_size = 100000 ## Cut column names at the given length to not exceed PostgreSQL's ## 'identifier length' limit (default: no limit) ## (see https://www.postgresql.org/docs/current/limits.html) ## Be careful to not create duplicate column names! # column_name_length_limit = 0 ## Enable &amp; set the log level for the Postgres driver. # log_level = "warn" # trace, debug, info, warn, error, none </code></pre>

Input and output integration examples

OpenStack

<ol> <li> <p><strong>Cross-Cloud Management</strong>: Leverage the OpenStack plugin to monitor and manage multiple OpenStack clouds from a single Telegraf instance. By aggregating metrics across different clouds, organizations can gain insights into resource utilization and optimize their cloud architecture for cost and performance.</p> </li> <li> <p><strong>Automated Scaling Based on Metrics</strong>: Integrate the metrics gathered from OpenStack into an automated scaling solution. For example, if the plugin detects that a specific service’s performance is degraded, it can trigger auto-scaling rules to launch additional instances, ensuring that system performance remains optimal under varying workloads.</p> </li> <li> <p><strong>Performance Monitoring Dashboard</strong>: Use data collected by the OpenStack Telegraf plugin to power real-time monitoring dashboards. This setup provides visualizations of key metrics from OpenStack services, enabling stakeholders to quickly identify trends, pinpoint issues, and make data-driven decisions in managing their cloud infrastructure.</p> </li> <li> <p><strong>Reporting and Analysis of Service Availability</strong>: By utilizing the metrics collected from various OpenStack services, teams can generate detailed reports on service availability and performance over time. This information can help identify recurring issues, improve service delivery, and make informed decisions regarding changes in infrastructure or service configuration.</p> </li> </ol>

TimescaleDB

<ol> <li> <p><strong>Real-Time IoT Data Ingestion</strong>: Use the plugin to collect and store sensor data from thousands of IoT devices in real time. This setup facilitates immediate analysis, helping organizations monitor operational efficiency and respond quickly to changing conditions.</p> </li> <li> <p><strong>Cloud Application Performance Monitoring</strong>: Leverage the plugin to feed detailed performance metrics from distributed cloud applications into TimescaleDB. This integration supports real-time dashboards and alerts, enabling teams to swiftly identify and mitigate performance bottlenecks.</p> </li> <li> <p><strong>Historical Data Analysis and Reporting</strong>: Implement a system where long-term metrics are stored in TimescaleDB for comprehensive historical analysis. This approach allows businesses to perform trend analysis, generate detailed reports, and make data-driven decisions based on archived time-series data.</p> </li> <li> <p><strong>Adaptive Alerting and Anomaly Detection</strong>: Integrate the plugin with automated anomaly detection workflows. By continuously streaming metrics to TimescaleDB, machine learning models can analyze data patterns and trigger alerts when anomalies occur, enhancing system reliability and proactive maintenance.</p> </li> </ol>

Feedback

Thank you for being part of our community! If you have any general feedback or found any bugs on these pages, we welcome and encourage your input. Please submit your feedback in the InfluxDB community Slack.

Useful Links

Documentation

Telegraf Quickstart Training

Infrastructure Monitoring with Telegraf

Powerful Performance, Limitless Scale

Collect, organize, and act on massive volumes of high-velocity data. Any data is more valuable when you think of it as time series data. with InfluxDB, the #1 time series platform built to scale with Telegraf.

See Ways to Get Started

Related Integrations

HTTP and InfluxDB Integration

The HTTP plugin collects metrics from one or more HTTP(S) endpoints. It supports various authentication methods and configuration options for data formats.

View Integration

Kafka and InfluxDB Integration

This plugin reads messages from Kafka and allows the creation of metrics based on those messages. It supports various configurations including different Kafka settings and message processing options.

View Integration

Kinesis and InfluxDB Integration

The Kinesis plugin allows for reading metrics from AWS Kinesis streams. It supports multiple input data formats and offers checkpointing features with DynamoDB for reliable message processing.

View Integration

Start building now

Download Telegraf today or learn more about InfluxDB.

telegraf Get started with InfluxDB
Product & Solutions
Developers
Company

548 Market St, PMB 77953
San Francisco, California 94104

© 2025 InfluxData Inc. All Rights Reserved.

Legal Security Cookie Policy Comparison