influxdb
Version information
This version is compatible with:
- Puppet Enterprise >= 3.0.0 < 2015.4.0
- Puppet >= 3.0.0 < 5.0.0
- , , ,
Start using this module
Add this module to your Puppetfile:
mod 'golja-influxdb', '4.0.0'
Learn more about managing modules with a PuppetfileDocumentation
InfluxDB
Table of Contents
- Overview
- Module Description - What the module does and why it is useful
- Installation
- Setup - The basics of getting started with influxdb
- Usage - Configuration options and additional functionality
- Reference - An under-the-hood peek at what the module is doing and how
- Limitations - OS compatibility, etc.
- Development - Guide for contributing to the module
- License
Overview
This module manages InfluxDB installation.
Module Description
The InfluxDB module manages both the installation and configuration of InfluxDB. I am planning to extend it to allow management of InfluxDB resources, such as databases, users, and privileges.
Deprecation Warning
Notes for version 4.0.0+:
influxdb 1.0.0 contains breaking changes
which require changing the data_logging_enabled
config attribute to trace_logging_enabled
.
The other configuration changes are managed by the influxdb.conf.erb
template already.
Notes for versions older than 3.1.1:
This release is a major refactoring of the module which means that the API changed in backwards incompatible ways. If your project depends on the old API and you need to use influxdb prior to 0.10.X, please pin your module dependencies to 0.1.2 (0.8.X) or 2.2.2 (0.9.X) version to ensure your environments don't break.
NOTE: Until influxdb 1.0.0 is releases the API of this module may change, however I will try my best to avoid it.
Installation
puppet module install golja/influxdb
Setup
What InfluxDB affects
- InfluxDB packages
- InfluxDB configuration files
- InfluxDB service
Beginning with InfluxDB
If you just want a server installed with the default options you can
run include '::influxdb::server'
.
Usage
All interaction for the server is done via influxdb::server
.
Install influxdb
class {'influxdb::server':}
Join a cluster
class {'influxdb::server':
meta_bind_address => "${::fqdn}:8088",
meta_http_bind_address => "${::fqdn}:8091",
http_bind_address => "${::fqdn}:8086",
influxd_opts => "-join my.other.node1:8091,my.other.node2:8091"
}
For more info on setting up a raft cluster, see the InfluxDB docs
Enable Graphite plugin with one database
class {'influxdb::server':
graphite_options => {
enabled => true,
database => graphite,
bind-address => ':2003',
protocol => tcp,
consistency-level => 'one',
name-separator => '.',
batch-size => 1000,
batch-pending => 5,
batch-timeout => '1s',
udp-read-buffer => 0,
name-schema => 'type.host.measurement.device',
templates => [ "*.app env.service.resource.measurement" ],
tags => [ "region=us-east", "zone=1c"],
},
}
Enable Collectd plugin
class {'influxdb::server':
collectd_options => {
enabled => true,
bind-address => ':25826',
database => 'foo',
typesdb => '/usr/share/collectd/types.db',
batch-size => 1000,
batch-pending => 5,
batch-timeout => '1s',
read-buffer => 0,
},
}
Enable UDP listener
$udp_options = [
{ 'enabled' => true,
'bind-address' => ':8089',
'database' => 'udp_db1',
'batch-size' => 10000,
'batch-timeout' => '1s',
'batch-pending' => 5,
},
{ 'enabled' => true,
'bind-address' => ':8090',
'database' => 'udp_db2',
'batch-size' => 10000,
'batch-timeout' => '1s',
'batch-pending' => 5,
},
]
class {'influxdb::server':
reporting_disabled => true,
http_auth_enabled => true,
shard_writer_timeout => '10s',
cluster_write_timeout => '10s',
udp_options => $udp_options,
}
Enable opentsdb
class {'influxdb::server':
opentsdb_options => {
enabled => true,
bind-address => ':4242',
database => 'foo',
typesdb => '/usr/share/collectd/types.db',
batch-size => 1000,
batch-pending => 5,
batch-timeout => '1s',
read-buffer => 0,
},
}
Reference
Classes
Public classes
influxdb::server
: Installs and configures InfluxDB.
Private classes
influxdb::server::install
: Installs packages.influxdb::server::config
: Configures InfluxDB.influxdb::server::service
: Manages service.
Parameters
influxdb::server
ensure
Allows you to install or remove InfluxDB. Can be 'present' or 'absent'.
version
Version of InfluxDB. Default: 0.9.3 NOTE: Unfortunately, the latest link available on the influxdb website is pointing to an old version. For more info, check ISSUE 3533
config_file
Path to the config file. Default: OS specific
service_provider
The provider to use to manage the service. Default: OS specific
service_enabled
Boolean to decide if the service should be enabled.
package_provider
What provider should be used to install the package.
meta_bind_address
This setting can be used to configure InfluxDB to bind to and listen for
cluster connections on this address, default is ":8088"
For clustering this must be set to <fqdn>:<port>
(usually 8088)
meta_http_bind_address
This setting can be used to configure InfluxDB to bind to and listen for
cluster connections on this address, default is ":8091"
For clustering this must be set to <fqdn>:<port>
(usually 8091)
reporting_disabled
If enabled once every 24 hours InfluxDB will report anonymous data to m.influxdb.com. Default: false
retention_autocreate
Default: true
election_timeout
Default: 1s
heartbeat_timeout
Default: 1s
leader_lease_timeout
Default: 500ms
commit_timeout
Default: 50ms
data_dir
Controls where the actual shard data for InfluxDB lives. Default: OS distro
wal_dir
Wal dir for the storage engine 0.9.3+ Default: /var/lib/influxdb/wal
meta_dir
Location of the meta dir Default: /var/lib/influxdb/meta
wal_enable_logging
Enable WAL logging. NEW in 0.9.3+ Default: true
shard_writer_timeout
The time within which a shard must respond to write. Default: 5s
cluster_write_timeout
The time within which a write operation must complete on the cluster. Default: 5s
retention_enabled
Controls the enforcement of retention policies for evicting old data. Default: true
retention_check_interval
Default: 10m
admin_enabled
Controls the availability of the built-in, web-based, admin interface. Default: true
admin_bind_address
Default: :8083
admin_https_enabled
If HTTPS is enabled for the admin interface, HTTPS must also be enabled on the [http] service. Default: false
admin_https_certificate
Default: undef
http_enabled
Controls how the HTTP endpoints are configured. These are the primary mechanism for getting data into and out of InfluxDB. Default: true
http_bind_address
Default: :8086
http_auth_enabled
Default: false
http_log_enabled
Default: true
http_write_tracing
Default: false
http_pprof_enabled
Default: false
http_https_enabled
Default: false
http_https_certificate
Default: undef
http_https_private_key
Default: undef
http_max_row_limit
Default: 10000
http_realm
Default: InfluxDB
subscriber_enabled
Controls the subscriptions, which can be used to fork a copy of all data received by the InfluxDB host. Default: true
subscriber_http_timeout
Default: 30s
graphite_options
Controls the listener for InfluxDB line protocol data via Graphite. Default: undef
collectd_options
Controls the listener for InfluxDB line protocol data via Collectd. Default: undef
opentsdb_options
Controls the listener for InfluxDB line protocol data via OpenTSDB. Default: undef
udp_options
Controls the listener for InfluxDB line protocol data via UDP. Default: undef
monitoring_enabled
Default: true
monitoring_write_interval
Default: 24h
monitoring_database
Default: _internal
continuous_queries_enabled
Controls how continuous queries are run within InfluxDB. Default: true
continuous_queries_log_enabled
Default true
continuous_queries_run_interval
Default: 1s
max_series_per_database
Controls the number of series allowed per database. Change the setting to 0 to allow an unlimited number of series per database. Default: 1000000
hinted_handoff_enabled
Controls the hinted handoff feature, which allows nodes to temporarily store queued data when one node of a cluster is down for a short period of time. Default: true
hinted_handoff_dir
Default: /var/lib/influxdb/hh
hinted_handoff_max_size
Default: 1073741824
hinted_handoff_max_age
Default: 168h
hinted_handoff_retry_rate_limit
Default: 0
hinted_handoff_retry_interval
Default: 1s
conf_template
If needed, you can add a custom template. Default: influxdb/influxdb.conf.erb
influxdb_user
Default: OS specific
influxdb_group
Default: OS specific
influxdb_stderr_log
Default: /var/log/influxdb/influxd.log
influxdb_stdout_log
Default: /dev/null
manage_install
enable/disable installation of the influxdb packages from the yum/apt repo Default: true
manage_repos
enable/disable repository installation Default: true
influxd_opts
Additional influxd options used for setting up raft clusters. Default: undef
Limitations
This module has been tested on:
- Ubuntu 12.04
- Ubuntu 14.04
- CentOS 6/7
Development
Please see CONTRIBUTING.md
Todo
- Add native types for managing users and databases
- Add more rspec tests
- Add beaker/rspec tests
License
See LICENSE file
##2016-10-24 - Release 4.0.0 ###Summary
- Official support for influxdb 1.0.0
##2016-06-06 - Release 3.1.1 ###Summary
- metadata updates (quality score update)
##2016-06-05 - Release 3.1.0 ###Summary
- Fix compatibility requirements
##2016-06-05 - Release 3.1.0 ###Summary
- Added support for external repositories
- Fix in the udp template
- autodetect service provider
##2016-03-13 - Release 3.0.1 ###Summary processing sorted hash sets for predictable template results
##2016-03-05 - Release 3.0.0 ###Summary Install influxdb from the official influxdata repository
####Backwards-incompatible changes
- Influxdata repository has only the latest 0.10.X version available. To manage version prior to 0.9.6 use previous modules, which install influxdb from the AWS S3 repository. I raised an issue https://github.com/influxdata/influxdb/issues/5913 asking influxdb maintainer to stop removing previous versions from the repos
- Now by default the module will install the latest version. To modify that overwrite version parameters
Special tnx to andyroyle for the 0.10.X fixes
##2015-12-11 - Release 2.2.0 ###Summary
- add meta_dir as a parameter
- adding INFLUXD_OPTS to /etc/default/influxdb. This is needed in setting up raft clusters.
##2015-12-11 - Release 2.1.1 ###Summary Explicitly import variables to make avoid compile error in puppet 4
##2015-11-26 - Release 2.1.0 ###Summary This release include support to manage install.
- add new parameter manage_install
##2015-11-05 - Release 2.0.0 ###Summary This release includes support for multiple UDP channels.
####Backwards-incompatible changes
Adding support for multiple UDP per database means we had to replace udp_enabled, udp_bind_address, udp_database, udp_batch_size and udp_batch_timeout with a more generic array of hashes (udp_options). For all the users not using UDP listener (disabled by default) won't have any problem upgrading the module to v2.0.0.
####Features
- Adds support for multiple UDP (tnx to bovy89)
####Bugfixes
- Fix documentation for proper use of collectd_database (tnx to Philipp Borgers)
##2015-10-23 - Release 1.1.1 ###Summary
- template fix for the UDP support
##2015-09-13 - Release 1.1.0 ###Summary
- Add support for 0.9.3 influxdb new config parameters
- Fix graphite template bug
- Default install version 0.9.3 - (we can't use latest version due to how influxdb is packaged)
Special tnx to Pedro González Serrano - NITEMAN for the graphite and 0.9.3 config template fix
##2015-08-25 - Release 1.0.1 ###Summary Improved the documentation and the module description
##2015-08-25 - Release 1.0.0 ###Summary Major module rewrite to support influxdb 0.9.X. For more info please check the README.md
##2015-01-25 - Release 0.1.2 ###Summary
- bugfix: specify the correct config file, because looks like the global settings are defined in /opt/influxdb/shared/config.toml
- bugfix: added missing RedHat/CentOS params to make it work properly (TODO: add system spec tests)
##2015-01-25 - Release 0.1.1 ###Summary
bugfix: correct package_source for RedHat osfamily
##2015-01-25 - Release 0.1.0 ###Summary
First public release.
Dependencies
- puppetlabs/stdlib (>= 1.0.0)
- puppetlabs/apt (>=1.8.0 <3.0.0)
Apache License Version 2.0, January 2004 http://www.apache.org/licenses/ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 1. Definitions. "License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document. "Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License. "Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity. "You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License. "Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files. "Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types. "Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below). "Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof. "Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution." "Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work. 2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form. 3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed. 4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions: (a) You must give any other recipients of the Work or Derivative Works a copy of this License; and (b) You must cause any modified files to carry prominent notices stating that You changed the files; and (c) You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and (d) If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License. You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License. 5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions. 6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file. 7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License. 8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages. 9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability. END OF TERMS AND CONDITIONS APPENDIX: How to apply the Apache License to your work. To apply the Apache License to your work, attach the following boilerplate notice, with the fields enclosed by brackets "[]" replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. We also recommend that a file or class name and description of purpose be included on the same "printed page" as the copyright notice for easier identification within third-party archives. Copyright 2013 Dejan Golja Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.