puppet_metrics_collector
Version information
This version is compatible with:
- Puppet Enterprise 2023.2.x, 2023.1.x, 2023.0.x, 2021.7.x, 2021.6.x, 2021.5.x, 2021.4.x, 2021.3.x, 2021.2.x, 2021.1.x, 2021.0.x, 2019.8.x, 2019.7.x, 2019.5.x, 2019.4.x, 2019.3.x, 2019.2.x, 2019.1.x, 2019.0.x, 2018.1.x
- Puppet >= 5.5.1 < 8.0.0
- , , , ,
Start using this module
Add this module to your Puppetfile:
mod 'puppetlabs-puppet_metrics_collector', '6.4.1'
Learn more about managing modules with a PuppetfileDocumentation
Table of Contents
Overview
This module collects metrics provided by the status endpoints of Puppet Enterprise services. The metrics can be used to identify performance issues that may be addressed by performance tuning.
For PE versions older than 2019.8.5, access to the
/metrics/v2
API endpoint is restricted tolocalhost
as a mitigation for CVE-2020-7943. This module requires access the/metrics/v2
API to collect a complete set of performance metrics from PuppetDB. Refer to Configuration for Distributed Metrics Collection for a workaround.
Setup
Installation
Install this module with puppet module install puppetlabs-puppet_metrics_collector
or add it to your Puppetfile.
To activate this module, classify your Primary Master (aka Master of Masters or MoM) with the puppet_metrics_collector
class using your preferred classification method.
Below is an example using site.pp
.
node 'master.example.com' {
include puppet_metrics_collector
}
Optionally, you can gather basic system metrics.
Unlike service metrics, system metrics have to be enabled locally on each PE Infrastructure Host, and the resulting data will be stored locally on that host.
This functionality depends on sysstat
.
node 'master.example.com' {
include puppet_metrics_collector
include puppet_metrics_collector::system
}
node 'compilerA.example.com', 'compilerB.example.com,' {
include puppet_metrics_collector::system
}
Note: Do not
include
the top-levelpuppet_metrics_collector
class on any PE Infrastructure Host other than the Primary Master, otherwise it will collect the same data as the Primary Master.
Configuration
This module automatically configures the hosts it collects metrics from by querying PuppetDB for PE Infrastructure Hosts. If there is an error with the automatic configuration of hosts, refer to Manual Configuration of Hosts.
Parameters
For each Puppet Enterprise service (Puppet Server, PuppetDB, Orchestrator, Ace, Bolt, and ActiveMQ) there are associated <service_name>_ensure
, <service_name>_hosts
, and <service_name>_port
parameters.
Refer to manifests/init.pp
for details.
output_dir
String
: Output directory for collected metrics.
Defaults to /opt/puppetlabs/puppet-metrics-collector
.
collection_frequency
Integer
: How often to collect metrics, in minutes.
Defaults to 5
.
retention_days
Integer
: How long to retain collect metrics, in days.
Defaults to 90
.
Metrics Server Parameters
The following set of parameters begining with metrics_server_
allows for the specification of a server type to use to generate and (in some cases) send data to a specified metrics server.
Currently, both influxdb
and graphite
types allow for the transfer of data while splunk_hec
only generates data.
metrics_server_type
Optional Enum['influxdb','graphite','splunk_hec']
: The metrics server type to send data to.
Currently, this module supports influxdb
, graphite
, and splunk_hec
metrics server types.
For the influxdb
metrics server type, a metrics_server_db_name
must be provided.
For the splunk_hec
metrics server type, data cannot be sent to a server, however the command will format the JSON output using the splunk_hec
module, which is a requirement for this option. The splunk_hec
module can be found on the Forge or GitHub.
Setup instructions for the splunk_hec
module can be found within that module's README.
metrics_server_hostname
Optional String
: The hostname of the metrics server to send data to.
Defaults to undef
.
metrics_server_port
Optional Integer
: The port number of the metrics server to send data to.
Defaults to undef
.
metrics_server_db_name
Optional String
: The database name on the metrics server to send data to.
Required for metrics_server_type
of influxdb
.
Defaults to undef
.
override_metrics_command
Optional String
: Allows you to define the command that is executed to gather metrics.
Defaults to undef
.
Usage
Grepping Metrics
Metrics are formatted as a JSON hash on one line.
In order to convert the metric files into a multi-line format, they can be processed with python -m json.tool
as per below.
cd /opt/puppetlabs/puppet-metrics-collector
for i in <service_name>/master.example.com/*.json; do echo "$(python -m json.tool < $i)" > $i; done
You can search for useful information by performing a grep
, run from inside the directory containing the metrics.
cd /opt/puppetlabs/puppet-metrics-collector
grep <metric_name> <service_name>/master.example.com/*.json
Since the metrics are archived once per day, you can only search metrics for the current day.
To search older metrics, decompress the archived files into a subdirectory of /tmp
and run your search from inside that directory.
Grepping Puppetserver Metrics
Example:
grep average-free-jrubies puppetserver/master.example.com/*.json
puppetserver/master.example.com/20190404T170501Z.json: "average-free-jrubies": 0.9950009285369501,
puppetserver/master.example.com/20190404T171001Z.json: "average-free-jrubies": 0.9999444653324225,
puppetserver/master.example.com/20190404T171502Z.json: "average-free-jrubies": 0.9999993830655706,
Grepping PuppetDB Metrics
Example:
grep queue_depth puppetdb/master.example.com/*.json
puppetdb/master.example.com/20190404T170501Z.json: "queue_depth": 0,
puppetdb/master.example.com/20190404T171001Z.json: "queue_depth": 0,
puppetdb/master.example.com/20190404T171502Z.json: "queue_depth": 0,
Sharing Metrics Data
When working with Support, you may be asked for an archive of collected metrics data.
This module provides a script, create-metrics-archive
to archive metrics data for sending to Support.
/opt/puppetlabs/puppet-metrics-collector/scripts/create-metrics-archive
This script creates the archive in the current working directory.
It takes an optional -m
or --metrics-directory
parameter (default /opt/puppetlabs/puppet-metrics-collector
) to specify an alterate metrics directory to archive.
It takes an optional -r
or --retention-days
parameter (default: 30
) to limit the number of days to include in the archive.
[root@master ~]# /opt/puppetlabs/puppet-metrics-collector/scripts/create-metrics-archive
Created metrics archive: /root/puppet-metrics-collector-20200203T123456Z.tar.gz
Reference
Directory Layout
This module creates an output directory with one subdirectory for each Puppet Enterprise service (Puppet Server, PuppetDB, Orchestrator, Ace, Bolt, and ActiveMQ) that this module has been configured to collect. Each service directory has one subdirectory for each host. Each host directory contains one JSON file, collected every 5 minutes. Once per day, the metrics for each service are archived and compressed.
Example:
/opt/puppetlabs/puppet-metrics-collector/puppetserver
├── master.example.com
│ ├── 20190404T020001Z.json
│ ├── ...
│ ├── 20190404T170501Z.json
│ └── 20190404T171001Z.json
└── puppetserver-2019.04.04.02.00.01.tar.gz
/opt/puppetlabs/puppet-metrics-collector/puppetdb
└── master.example.com
│ ├── 20190404T020001Z.json
│ ├── ...
│ ├── 20190404T170501Z.json
│ ├── 20190404T171001Z.json
└── puppetdb-2019.04.04.02.00.01.tar.gz
Cron Jobs
This module creates two cron jobs for each Puppet Enterprise service:
- A cron job to collect the metrics
- Runs as per
collection_frequency
- Runs as per
- A cron job to archive collected metrics and delete metrics older than the retention period, as per
retention_days
- Runs at randomly selected time between 12:00 AM and 3:00 AM
Example:
crontab -l
...
# Puppet Name: puppetserver_metrics_collection
*/5 * * * * /opt/puppetlabs/puppet-metrics-collector/scripts/tk_metrics --metrics_type puppetserver --output_dir /opt/puppetlabs/puppet-metrics-collector/puppetserver
# Puppet Name: puppetserver_metrics_tidy
0 2 * * * /opt/puppetlabs/puppet-metrics-collector/scripts/metrics_tidy /opt/puppetlabs/puppet-metrics-collector puppetserver 90
Alternate Setup
Temporary Installation
While a permanent installation is recommended, this module can be temporarily installed with the following commands.
puppet module install puppetlabs-puppet_metrics_collector --modulepath /tmp;
puppet apply -e "class { 'puppet_metrics_collector': }" --modulepath /tmp;
Manual Configuration of Hosts
If necessary, you can manually configure this module by specifying parameters via the class declaration or via Hiera data. The preferred method is via Hiera data. The following examples show you how to specify those parameters for different infrastructures, and assumes you declare this module on the Primary Master.
Monolithic Infrastructure with Compile Masters
Hiera Data Example
puppet_metrics_collector::puppetserver_hosts:
- 'master.example.com'
- 'compile-master-1.example.com'
- 'compile-master-2.example.com'
puppet_metrics_collector::puppetdb_hosts:
- 'master.example.com'
Class Declaration Example
class { 'puppet_metrics_collector':
puppetserver_hosts => [
'master.example.com',
'compile-master-1.example.com',
'compile-master-2.example.com'
],
puppetdb_hosts => ['master.example.com'],
}
Split Infrastructures without Compile Masters
Hiera Data Example
puppet_metrics_collector::puppetserver_hosts:
- 'split-master.example.com'
puppet_metrics_collector::puppetdb_hosts:
- 'split-puppetdb.example.com'
Class Declaration Example
class { 'puppet_metrics_collector':
puppetserver_hosts => ['split-master.example.com'],
puppetdb_hosts => ['split-puppetdb.example.com'],
}
Split Infrastructure with Compile Masters
Hiera Data Example
puppet_metrics_collector::puppetserver_hosts:
- 'split-master.example.com'
- 'compile-master-1.example.com'
- 'compile-master-2.example.com'
puppet_metrics_collector::puppetdb_hosts:
- 'split-puppetdb.example.com'
Class Definition Example
class { 'puppet_metrics_collector':
puppetserver_hosts => [
'split-master.example.com',
'compile-master-1.example.com',
'compile-master-2.example.com'
],
puppetdb_hosts => ['split-puppetdb.example.com'],
}
Configuration for Distributed Metrics Collection
This option collect metrics on each PE Infrastructure Host instead of collecting metrics centrally on the Primary Master. This option is discouraged, but allows for the collection of metrics when the Primary Master cannot access the API endpoints of the other PE Infrastructure Hosts. Classify each PE Infrastructure Host with this module, specifying the following parameters.
When classifying a Compile Master, specify these additional parameters:
class { 'puppet_metrics_collector':
puppetserver_hosts => ['127.0.0.1'],
puppetdb_metrics_ensure => absent,
orchestrator_metrics_ensure => absent,
ace_metrics_ensure => absent,
bolt_metrics_ensure => absent,
}
When classifying a PuppetDB Host, specify these additional parameters:
class { 'puppet_metrics_collector':
puppetdb_hosts => ['127.0.0.1'],
puppetserver_metrics_ensure => absent,
orchestrator_metrics_ensure => absent,
ace_metrics_ensure => absent,
bolt_metrics_ensure => absent,
}
Patch Release 6.4.1
Changes:
- Standardize cleanup of temp files #88
Minor Release 6.4.0
Improvements
- Clean up temp files when metrics_tidy exits cleanly #86
- Enable client ssl cert for metrics #82
- Update to PDK 2.0, Updated Supported Puppet versions, and OS's #83
Changes:
- Re-enable remote metric collection #85
Minor Release 6.3.0
Improvements
- Update json2timeseriesdb to tag Postgres metrics #79
Changes:
- Fix psql_metrics error checking #78
Minor Release 6.2.0
Improvements
Changes:
- Mbeans that return a 404 will default to null instead of an error #76
- A warning is no longer printed when shipping metrics to a remote database #75
- Fix duplicate declaration of common files #70
- Fix ensure => absent for metrics #69
Patch Release 6.1.1
Changes:
- Fixes a bug where Orchestrator metrics collection used the Puppetserver parameters
Minor Release 6.1.0
Improvements
- Fixes a bug where the tarballs files would contain 90 days worth of files instead of 1
- Ensure the system metrics can be tidied up
- Stop pretty-printing the system metrics.
Major Release 6.0.0
This is a major release as it drops support for Puppet 4.x and versions of PE based upon Puppet 4.x. If you are using those unsupported versions of PE, continue to use version 5.3.0.
Refer to the README for limitations regarding the collection of remote PuppetDB metrics, and a workaround.
If using this module with the Puppet Metrics Dashboard, upgrade to version 2.2.0 or later of that module.
Improvements
- Switch from the v1 to v2 Metrics API for additional metrics (for PuppetDB)
- Collect ACE and Bolt service metrics
- Reorganize into service and system classes
- Move duplicate code from service classes to defined types
- Move templated per-service tidy scripts to one common 'metrics_tidy' script
- Simplify the 'create-metrics-archive' script, removing the one constant parameter
- Do not symlink the 'create-metrics-archive' script to '/opt/puppetlabs/bin/'
- Store configuration and code in separate 'config' and 'scripts' directories
- Eliminate the '/opt/puppetlabs/puppet_metrics_collector/bin' directory
- Add puppet code to delete the resulting legacy directories and files
- Resolve various puppet-lint and rubocop issues
- Refactor the shell scripts
- Merge json2graphite.rb and json2timeseriesdb scripts
- Update measurement tagging
- Update to PDK 1.16
- Update documentation
Changes
- Drop support for Puppet 4.x and versions of PE based upon Puppet 4.x
- Use v2 Metrics API for additional metrics for PuppetDB
- Change tags to system metrics
Minor Release 5.3.0
Improvements
- Enable FOSS support with Puppetserver collection
- Remove
127.0.0.1
special case naming - Add the ability to generate system metrics
- Make the output files smaller by excluding metrics and not pretty printing
Changes
- Add a newline to STDOUT of the processing script
Minor Release 5.2.0
Improvements
- Add ability to send metrics data directly to influxdb, graphite, or splunk ( in combination with the splunk_hec module )
Changes
- Update metadata dependency information to reflect support for puppetlabs/stdlib 6.x
Patch Release 5.1.2
Changes:
- Update metadata dependency information to reflect support for puppetlabs/stdlib 5.x
- Update Changelog terminology to use semver term "Patch", rather than "Z"
Patch Release 5.1.1
Changes:
- Ensure nightly compression of metrics works with a large amount of files
Minor Release 5.1.0
Improvements
- Auto configure puppetserver and puppetdb hosts
- https://github.com/puppetlabs/puppetlabs-puppet\_metrics\_collector/pull/5
Patch Release 5.0.1
Changes:
- Convert module to standard PDK format
Major Release 5.0.0
This major release renames the project and obseletes deprecated parameters that had previously been preserved for backwards compatiblity. The new name of the project aligns it with the value it provides, and eliminates long incorrect technology references to its implementation from the name.
Note: If upgrading to puppet_metrics_collector 5.x from a pe_metric_curl_cron_jobs version older than 4.6.0, it is recommended that you deploy pe_metric_curl_cron_jobs 4.6.0 first, let Puppet run, and then upgrade to puppet_metrics_collector 5.x in order to ensure that all cleanup and migration work is performed smoothly.
Changes
- Rename the project from "pe_metric_curl_cron_jobs" to "puppet_metrics_collector"
- Remove deprecated parameters
- puppet_metrics_collector::puppet_server_hosts (long deprecated in favor of puppet_metrics_collector::puppetserver_hosts)
- puppet_metrics_collector::puppet_server_port (long deprecated in favor of puppet_metrics_collector::puppetserver_port)
Minor Release 4.6.0
Improvements:
- Add PuppetDB HA Metrics
Minor Release 4.5.0
Improvements:
- Add a script to zip up metrics for sharing
Patch Release 4.4.2
Bug Fixes:
- Tidy script does not work without bzip (not installed on RHEL 7 by default)
- The tidy script now uses gzip which is more regularly available
- PR #45
- Tidy script would not exit on error
- Config file could change every run if you use puppetdb_query to find the hosts
Patch Release 4.4.1
Bug Fixes:
- PuppetDB metrics could not be gathered by default in PE < 2016.4.0
Minor Release 4.4.0
Improvements
- Allow connecting over http instead of https for PuppetDB
- PR #37
- In order to use pass
--no-ssl
and--metrics_port
to the tk_metrics script
Minor Release 4.3.0
Improvements
- No longer pass certificates to connect to metrics endpoint
Patch Release 4.2.2
Bug Fixes:
- Tidy cron jobs would only delete metric files exactly retention_days away
Patch Release 4.2.1
Bug Fixes:
- PE versions < 2016.2 now GET each metric individually instead of using a POST
Minor Release 4.2.0
Improvements
- Allow not saving a metrics file
- Add a
--output-dir
CLI argument to metrics scripts which tells the script where to save metrics output to. - If
--output-dir
is not specified then no file is saved
- Add a
- Metrics scripts print to STDOUT by default
- Use
--no-print
to silence output to STDOUT
- Use
Minor Release 4.1.0
Improvements
- Retrieve all additional metrics with one POST instead of multiple GETs
- Add a
--print
command line argument to the metrics scripts- This allows for integrations with other tools that can read the output from stdout.
- PR #24
- Move script configuration into a YAML file
- Allow the metrics scripts to be stored as static files instead of templates
- PR #25
Major Release 4.0.0
This is a major release because some of the PuppetDB metrics are renamed. For most users this update is only additive, however, if you are post processing the output of the module then you may need to update to the new names of the metrics.
Changes
- Rename some PuppetDB metrics
- command_processing_time is now global_processing_time
- command_processed is now global_processed
- replace_catalog_time is now storage_replace-catalog-time
- replace_facts_time is now storage_replace-facts-time
- store_report_time is now storage_store-report-time
- _retry and _retry-counts metrics are renamed to include mq_ at the front
Improvements
- We now collect the output of the status endpoint for orchestrator
- We now collect HakariCP connection pooling metrics for PuppetDB
- We now collect the global metrics for PuppetDB
- We now collect the storage metrics for PuppetDB
- Each component now has its own class to allow customizing parameters per component
Patch Release 3.0.1
Bug Fixes:
- Stagger compression of files between midnight and 3AM to prevent a CPU spike
Major Release 3.0.0
Changes
- Every parameter, file name, etc... that contained puppet_server is rewritten
to puppetserver
- The existing parameters remain but are deprecated and should not be used
- Metric storage format is a single JSON blob instead of the exact output from whichever endpoint was queried
Improvements
- Metrics gathering scripts are rewritten in ruby
- Metrics are now stored in one file per component
- PuppetDB metrics were previously stored with one file per metric
- Metrics are now stored in one directory per server
- PuppetDB metrics now gathers the status endpoint
- This is the preferred way to get the queue_depth metric
- Opt-in collection of ActiveMQ metrics is available
- Metrics are compressed daily for a 90% reduction in disk space
- Metrics are retained for 90 days by default instead of 3 days
- Retained metrics still take less space due to compression savings
- Metrics are retained for 90 days by default instead of 3 days
Bug Fixes:
- The metrics tidy cron job previously ran every minute between 2-3 AM. It now runs just once at 2AM.
Dependencies
- puppetlabs-stdlib (>= 2.6.0 < 8.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 2016 Nick Walker 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.