What's new in InfluxDB OSS 1.5
For a comprehensive list of the changes between versions, see InfluxDB Release Notes/Changelog.
Included here are some highlights of the InfluxDB OSS 1.5 release:
- Time Series Index (TSI) support
- Enterprise-compatible backup and restore
- Structured logging
- Redirecting HTTP request logging
- InfluxDB ‘/metrics’ HTTP endpoint
Time Series Index (TSI) support
InfluxDB 1.5 introduced support for the InfluxDB time series index (TSI) disk-based storage engine. TSI was first introduced in InfluxDB 1.3 as a technical preview. Since then, InfluxDB users and InfluxData have tested, used, and shared feedback on this functionality.
With TSI, the number of series should be unbounded by the memory on the server hardware and the number of existing series will have a negligible impact on database startup time.
For more details on TSI, see the following:
Note: TSI remains disabled by default in InfluxDB 1.5, but you are encouraged to enable and use TSI to enhance the management of time series data, especially for data with high series cardinality. You can always revert to in-memory indexing, if required.
Enterprise-compatible backup and restore for InfluxDB OSS
Note: For InfluxDB Enterprise clusters, see Backing up and restoring in InfluxDB Enterprise.
Starting with InfluxDB 1.5, InfluxDB OSS supports enterprise-compatible backup and restore. The InfluxDB OSS
backup utility provides:
- Option to run backup and restore functions on an online, or live, database.
- Backup and restore functions for single or multiple databases with optional filtering based on data point timestamps.
- Data imports from InfluxDB Enterprise clusters
- Backup files that can be imported into an InfluxDB Enterprise database.
restore utility in InfluxDB OSS supports the new Enterprise-compatible backup format, but the the legacy backup format is still available.
For details about the new backup and restore functionality, see Backing up and restoring in InfluxDB OSS.
With InfluxDB 1.5, logging has been improved to support structured logging, trace logs, and generating HTTP request logs separate from InfluxDB internal logs.
Structured logging support allows you to more easily integrate InfluxDB logs with Splunk, Papertrail, Elasticsearch, and other third party tools. The two new structured log formats,
json, provide machine-readable and more developer-friendly log outputs.
See Structured logging.
Logging has been enhanced to provide tracing of important InfluxDB operations. Tracing is useful for error reporting and discovering performance bottlenecks.
For details on the tracing keys, tooling, and examples, see Tracing.
Redirecting HTTP request logging
InfluxDB 1.5 introduces the option to log HTTP request traffic separately from the other InfluxDB log output. When HTTP request logging is enabled, the HTTP logs are intermingled by default with internal InfluxDB logging. By redirecting the HTTP request log entries to a separate file, both log files are easier to read, monitor, and debug.
For more information, see Redirecting HTTP request logging.
InfluxDB ‘/metrics’ HTTP endpoint
A new InfluxDB ‘/metrics’ HTTP endpoint is configured to produce the default Go metrics in Prometheus metrics format. For details, see InfluxDB
/metrics HTTP endpoint
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, the following resources are available:
InfluxDB Cloud and InfluxDB Enterprise customers can contact InfluxData Support.