puppet_operational_dashboards
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, 2017.3.x, 2017.2.x, 2017.1.x, 2016.5.x, 2016.4.x
- Puppet >= 4.7.0 < 8.0.0
- , , , ,
Start using this module
Add this module to your Puppetfile:
mod 'puppetlabs-puppet_operational_dashboards', '0.2.0'
Learn more about managing modules with a PuppetfileDocumentation
puppet_operational_dashboards
Table of Contents
- Description
- Setup - The basics of getting started with puppet_operational_dashboards
- Usage - Configuration options and additional functionality
Description
This module is a replacement for the puppet_metrics_dashboard module. It is used to configure Telegraf, InfluxDB, and Grafana to collect, store, and display metrics collected from Puppet services. By default, those components are installed on a separate Dashboard node by applying the base class of this module to that node. That class will automatically query PuppetDB for Puppet Infrastructure nodes (Primary server, Compilers, PuppetDB hosts, PostgreSQL hosts) or you can specify them via associated class parameters. It is not recommended to apply the base class of this module to one of your Puppet Infrastructure nodes.
Setup
Prerequisites
The toml-rb gem needs to be installed in the Puppetserver gem space, which can be done with the influxdb::profile::toml class in the InfluxDB module.
To collect PostgreSQL metrics, classify your PostgreSQL nodes with the puppet_operational_dashboards::profile::postgres_access class. FOSS users will need to manually configure the PostgreSQL authentication settings.
Beginning with puppet_operational_dashboards
The easiest way to get started using this module is by including the puppet_operational_dashboards
class to install and configure Telegraf, InfluxDB, and Grafana. Note that you also need to install the toml-rb gem according to the prerequisites.
include puppet_operational_dashboards
Doing so will:
- Install and configure InfluxDB using the puppetlabs/influxdb module
- Install and configure Telegraf to collect metrics from your PE infrastructure. FOSS users can specify a list of infrastructure nodes via the
puppet_operational_dashboards::telegraf::agent
parameters. - Install and configure Grafana with several dashboards to display data from InfluxDB
Note that this will save an InfluxDB administrative token to the user's home directory, typically /root/.influxdb_token
. The puppetlabs/influxdb
types and providers can make use of this file during catalog application. The manifests in this module are also able to use it via deferred functions, which also run on the agent as the first step of catalog application. Therefore, it is possible to use this file for all token-based operations in this module, and no further configuration is required.
It is also possible to specify this token via the influxdb::token
parameter in hiera. The Telegraf token used by the telegraf
service and Grafana datasource can also be set via puppet_operational_dashboards::telegraf_token
. These are both Sensitive
strings, so the recommended way to use them is to encrypt them with hiera-eyaml and use the encrypted value in hiera data. After setting up a hierarchy to use the eyaml backend, the values can be added to hiera data and automatically converted to Sensitive
:
influxdb::token: <eyaml_encrypted_string>
lookup_options:
influxdb::token:
convert_to: "Sensitive"
These parameters take precedence over the file on disk if both are specified.
Usage
Determining where Telegraf runs
Which hosts a node collects metrics from is determined by the puppet_operational_dashboards::telegraf::agent::collection_method
parameter. By default, the puppet_operational_dashboards
class will collect metrics from all nodes in a PE infrastructure. If you want to change this behavior, set collection_method
to local
or none
. Telegraf can be run on other nodes by applying the puppet_operational_dashboards::telegraf::agent
class to them, for example:
class {'puppet_operational_dashboards::telegraf::agent':
collection_method => 'local',
token => <my_sensitive_token>,
}
Importing archive metrics
Metrics archives output by the Puppet metrics collector can be imported into InfluxDB using the scripts in the examples/
directory. The sample bucket_and_datasource
class shows how to configure an InfluxDB bucket and Grafana datasource, while the Telegraf files can be used to load the data into the bucket. After setting up the bucket and datasource:
- Download the
telegraf.conf
andtelegraf.conf.d
files to your home directory. - Extract the archive
tar xf <metrics_gz>
cd <output_directory>
- Delete any Puppet server metrics with errors.
Currently, these will cause the telegraf
process to exit upon encountering an error. Delete these with:
find <puppet_server_metrics_dir> -type f -name "*json" -size -1000c -delete
- Edit
telegraf.conf
to point to your bucket (<my_bucket>
) and InfluxDB server (<influxdb_fqdn>
). - Export your Telegraf token
export INFLUX_TOKEN=<token>
This token can be found in the "API Tokens" tab of the "Data" page in InfluxDB
- Run Telegraf to import the metrics. This can be done all at once:
telegraf --once --debug --config ~/telegraf.conf --config-directory ~/telegraf.conf.d/
Or one service at a time, e.g. for Puppet server
telegraf --once --debug --config ~/telegraf.conf --config ~/telegraf.conf.d//puppetserver.conf
Reference
Table of Contents
Classes
puppet_operational_dashboards
: Installs Telegraf, InfluxDB, and Grafana to collect and display Puppet metricspuppet_operational_dashboards::profile::dashboards
: Installs Grafana and several dashboards to display Puppet metrics. Included via the base class.puppet_operational_dashboards::profile::postgres_access
: Allows Telegraf to connect and collect metrics from postgres nodespuppet_operational_dashboards::telegraf::agent
: Installs and configures Telegraf to query hosts in a Puppet infrastructure. Included by the base class
Defined types
puppet_operational_dashboards::telegraf::config
: Defined type to create Telegraf configurations for a given service
Functions
puppet_operational_dashboards::hosts_with_profile
puppet_operational_dashboards::pe_profiles_on_host
: function used to determine hosts with a Puppet Enterprise profile
Classes
puppet_operational_dashboards
Installs Telegraf, InfluxDB, and Grafana to collect and display Puppet metrics
Examples
Basic usage
include puppet_operational_dashboards
class {'puppet_operational_dashboards':
manage_influxdb => false,
influxdb_host => '<influxdb_fqdn>',
}
Parameters
The following parameters are available in the puppet_operational_dashboards
class:
manage_influxdb
manage_grafana
influxdb_host
influxdb_port
initial_org
initial_bucket
influxdb_token
telegraf_token_name
manage_telegraf
manage_telegraf_token
use_ssl
influxdb_token_file
manage_influxdb
Data type: Boolean
Whether to manage installation and configuration of InfluxDB. Defaults to true
Default value: true
manage_grafana
Data type: Boolean
Whether to manage installation and configuration of Grafana. Defaults to true
Default value: true
influxdb_host
Data type: String
FQDN of the InfluxDB host. Defaults to a the value of influxdb::host, or $facts['fqdn'] if unset
Default value: lookup(influxdb::host, undef, undef, $facts['networking']['fqdn'])
influxdb_port
Data type: Integer
Port used by the InfluxDB service. Defaults to the value of influxdb::port, or 8086 if unset
Default value: lookup(influxdb::port, undef, undef, 8086)
initial_org
Data type: String
Name of the InfluxDB organization to configure. Defaults to the value of influxdb::initial_org, or 'puppetlabs' if unset
Default value: lookup(influxdb::initial_org, undef, undef, 'puppetlabs')
initial_bucket
Data type: String
Name of the InfluxDB bucket to configure and query. Defaults to the value of influxdb::initial_bucket, or 'puppet_data' if unset
Default value: lookup(influxdb::initial_bucket, undef, undef, 'puppet_data')
influxdb_token
Data type: Optional[Sensitive[String]]
InfluxDB admin token in Sensitive format. Defaults to the value of influxdb::token. See the puppetlabs/influxdb documentation for more information about this token.
Default value: lookup(influxdb::token, undef, undef, undef)
telegraf_token_name
Data type: String
Name of the token to retrieve from InfluxDB if not given $telegraf_token.
Default value: 'puppet telegraf token'
manage_telegraf
Data type: Boolean
Whether to manage installation and configuration of Telegraf. Defaults to true.
Default value: true
manage_telegraf_token
Data type: Boolean
Whether to create and manage a Telegraf token with permissions to query buckets in the default organization. Defaults to true.
Default value: true
use_ssl
Data type: Boolean
Whether to use SSL when querying InfluxDB. Defaults to true
Default value: true
influxdb_token_file
Data type: String
Location on disk of an InfluxDB admin token. This file is written to by the influxdb class during installation and read by the type and providers, as well Deferred functions in this module.
Default value: lookup(influxdb::token_file, undef, undef, $facts['identity']['user'] ? { 'root' => '/root/.influxdb_token', default => "/home/${facts['identity']['user']}/.influxdb_token" })
puppet_operational_dashboards::profile::dashboards
Installs Grafana and several dashboards to display Puppet metrics. Included via the base class.
Examples
Basic usage
include puppet_operational_dashboards
class {'puppet_operational_dashboards::profile::dashboards':
token => '<my_sensitive_token>',
influxdb_host => '<influxdb_fqdn>',
influxdb_port => 8086,
initial_bucket => '<my_bucket>',
}
Parameters
The following parameters are available in the puppet_operational_dashboards::profile::dashboards
class:
token
grafana_host
grafana_port
grafana_password
grafana_version
grafana_datasource
grafana_install
use_ssl
manage_grafana_repo
influxdb_host
influxdb_port
influxdb_bucket
telegraf_token_name
influxdb_token_file
token
Data type: Optional[Sensitive[String]]
Token in Sensitive format used to query InfluxDB. The token must grant priviledges to query the associated bucket in InfluxDB
Default value: undef
grafana_host
Data type: String
FQDN of the Grafana host. Defaults to the FQDN of the agent receiving the catalog.
Default value: $facts['networking']['fqdn']
grafana_port
Data type: Integer
Port used by the Grafana service. Defaults to 3000
Default value: 3000
grafana_password
Data type: Sensitive[String]
Grafana admin password in Sensitive format. Defaults to 'admin'
Default value: Sensitive('admin')
grafana_version
Data type: String
Version of the Grafana package to install. Defaults to '8.2.2'
Default value: '8.2.2'
grafana_datasource
Data type: String
Name to use for the Grafana datasource. Defaults to 'influxdb_puppet'
Default value: 'influxdb_puppet'
grafana_install
Data type: String
Method to use for installing Grafana. Defaults to using a repository on EL and Debian/Ubuntu, and package for other platforms
Default value: $facts['os']['family']
use_ssl
Data type: Boolean
Whether to use SSL when querying InfluxDB. Defaults to true
Default value: true
manage_grafana_repo
Data type: Boolean
Whether to manage the Grafana repository definition. Defaults to true.
Default value: true
influxdb_host
Data type: String
FQDN of the InfluxDB host. Defaults to the value of the base class, which looks up the value of influxdb::host with a default of $facts['fqdn']
Default value: $puppet_operational_dashboards::influxdb_host
influxdb_port
Data type: Integer
Port used by the InfluxDB service. Defaults to the value of the base class, which looks up the value of influxdb::port with a default of 8086
Default value: $puppet_operational_dashboards::influxdb_port
influxdb_bucket
Data type: String
Name of the InfluxDB bucket to query. Defaults to the value of the base class, which looks up the value of influxdb::initial_bucket with a default of 'puppet_data'
Default value: $puppet_operational_dashboards::initial_bucket
telegraf_token_name
Data type: String
Name of the token to retrieve from InfluxDB if not given $token
Default value: $puppet_operational_dashboards::telegraf_token_name
influxdb_token_file
Data type: String
Location on disk of an InfluxDB admin token. This token is used in this class in a Deferred function call to retrieve a Telegraf token if $token is unset
Default value: $puppet_operational_dashboards::influxdb_token_file
puppet_operational_dashboards::profile::postgres_access
Allows Telegraf to connect and collect metrics from postgres nodes
Examples
Basic usage
include puppet_operational_dashboards::profile::postgres_access
Parameters
The following parameters are available in the puppet_operational_dashboards::profile::postgres_access
class:
telegraf_hosts
Data type: Array
A list of FQDNs running Telegraf to allow access to
Default value: puppet_operational_dashboards::hosts_with_profile('Puppet_operational_dashboards::Telegraf::Agent')
puppet_operational_dashboards::telegraf::agent
Installs and configures Telegraf to query hosts in a Puppet infrastructure. Included by the base class
Examples
Basic usage
include puppet_operational_dashboards
class {'puppet_operational_dashboards::telegraf::agent':
token => '<sensitive_telegraf_token>',
}
Parameters
The following parameters are available in the puppet_operational_dashboards::telegraf::agent
class:
token
influxdb_host
influxdb_port
influxdb_org
influxdb_bucket
use_ssl
manage_ssl
ssl_cert_file
ssl_key_file
ssl_ca_file
version
collection_method
collection_interval
puppetserver_hosts
puppetdb_hosts
postgres_hosts
profiles
local_services
token_name
influxdb_token_file
token
Data type: Optional[Sensitive[String]]
Telegraf token in Sensitive format.
Default value: undef
influxdb_host
Data type: String
FQDN of the InfluxDB host. Defaults to $facts['fqdn']
Default value: $puppet_operational_dashboards::influxdb_host
influxdb_port
Data type: Integer
Port used by the InfluxDB service. Defaults to 8086.
Default value: $puppet_operational_dashboards::influxdb_port
influxdb_org
Data type: String
Name of the InfluxDB organization. Defaults to 'puppetlabs'.
Default value: $puppet_operational_dashboards::initial_org
influxdb_bucket
Data type: String
Name of the InfluxDB bucket to query. Defaults to 'puppet_data'.
Default value: $puppet_operational_dashboards::initial_bucket
use_ssl
Data type: Boolean
Whether to use SSL when querying InfluxDB. Defaults to true
Default value: true
manage_ssl
Data type: Boolean
Whether to manage Telegraf ssl configuration. Defaults to true.
Default value: true
ssl_cert_file
Data type: String
SSL certificate to be used by the telegraf service. Defaults to the agent certificate issued by the Puppet CA for the local machine.
Default value: "/etc/puppetlabs/puppet/ssl/certs/${trusted['certname']}.pem"
ssl_key_file
Data type: String
Private key used in the CSR for the certificate specified by $ssl_cert_file. Defaults to the private key of the local machine for generating a CSR for the Puppet CA
Default value: "/etc/puppetlabs/puppet/ssl/private_keys/${trusted['certname']}.pem"
ssl_ca_file
Data type: String
CA certificate issued by the CA which signed the certificate specified by $ssl_cert_file. Defaults to the Puppet CA.
Default value: '/etc/puppetlabs/puppet/ssl/certs/ca.pem'
version
Data type: String
Version of the Telegraf package to install. Defaults to '1.21.2'.
Default value: '1.21.2'
collection_method
Data type: Enum['all', 'local', 'none']
Determines how metrics will be collected. 'all' will query all Puppet services across all Puppet infrastructure hosts from the node with this class applied. 'local' will query all Puppet services on the node with this class applied. TODO 'none' will not query any services from the node with this class applied.
Default value: 'all'
collection_interval
Data type: String
How frequently to collect metrics. Defaults to '10m'.
Default value: '10m'
puppetserver_hosts
Data type: Array
Array of Puppet server hosts to collect metrics from. Defaults to all Puppet server hosts in a PE infrastructure. FOSS users need to supply a list of FQDNs
Default value: puppet_operational_dashboards::hosts_with_profile('Puppet_enterprise::Profile::Master')
puppetdb_hosts
Data type: Array
Array of PuppetDB hosts to collect metrics from. Defaults to all PuppetDB hosts in a PE infrastructure. FOSS users need to supply a list of FQDNs
Default value: puppet_operational_dashboards::hosts_with_profile('Puppet_enterprise::Profile::Puppetdb')
postgres_hosts
Data type: Array
Array of Postgres hosts to collect metrics from. Defaults to all Postgres in a PE infrastructure. FOSS users need to supply a list of FQDNs.
Default value: puppet_operational_dashboards::hosts_with_profile('Puppet_enterprise::Profile::Database')
profiles
Data type: Array[String]
Array of PE profiles on the node with this class applied. Used when collection_method is set to 'local'. FOSS users can use the $local_services parameter.
Default value: puppet_operational_dashboards::pe_profiles_on_host()
local_services
Data type: Array[String]
Array of FOSS services to collect from when collection_method is set to 'local'.
Default value: []
token_name
Data type: String
Name of the token to retrieve from InfluxDB if not given $token
Default value: $puppet_operational_dashboards::telegraf_token_name
influxdb_token_file
Data type: String
Location on disk of an InfluxDB admin token. This token is used in this class in a Deferred function call to retrieve a Telegraf token if $token is unset
Default value: $puppet_operational_dashboards::influxdb_token_file
Defined types
puppet_operational_dashboards::telegraf::config
Defined type to create Telegraf configurations for a given service
Parameters
The following parameters are available in the puppet_operational_dashboards::telegraf::config
defined type:
service
Data type: String
Name of the service to query. Is the title of the resource.
Default value: $title
hosts
Data type: Array[String[1]]
Array of hosts running the service
ensure
Data type: Enum['present', 'absent']
Whether the resource should be present or absent
Default value: 'present'
Functions
puppet_operational_dashboards::hosts_with_profile
Type: Puppet Language
The puppet_operational_dashboards::hosts_with_profile function.
puppet_operational_dashboards::hosts_with_profile(String $profile)
The puppet_operational_dashboards::hosts_with_profile function.
Returns: Array[String]
profile
Data type: String
puppet_operational_dashboards::pe_profiles_on_host
Type: Puppet Language
Queries PuppetDB for Puppet Enterprise profile on the node including the class. Used by this module to identify Puppet Enterprise API endpoints on the node.
puppet_operational_dashboards::pe_profiles_on_host()
Queries PuppetDB for Puppet Enterprise profile on the node including the class. Used by this module to identify Puppet Enterprise API endpoints on the node.
Returns: Array[String]
An array of PE profiles representing the Puppet server, PDB, and postgres services
Change log
All notable changes to this project will be documented in this file. The format is based on Keep a Changelog and this project adheres to Semantic Versioning.
v0.2.0 (2022-03-11)
Added
Fixed
v0.1.2 (2022-03-08)
Fixed
v0.1.1 (2022-03-08)
Fixed
* This Changelog was automatically generated by github_changelog_generator
Dependencies
- puppet-grafana (>= 10.0.0 < 11.0.0)
- puppet-telegraf (>= 4.1.0 < 5.0.0)
- puppetlabs-apt (>= 4.3.0 < 9.0.0)
- puppetlabs-inifile (>= 2.0.0 < 6.0.0)
- puppetlabs-influxdb (>= 0.3.0 < 1.0.0)
- puppetlabs-stdlib (>= 1.0.0 < 9.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 2018 Erik Hansen 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.
Quality checks
We run a couple of automated scans to help you assess a module’s quality. Each module is given a score based on how well the author has formatted their code and documentation and select modules are also checked for malware using VirusTotal.
Please note, the information below is for guidance only and neither of these methods should be considered an endorsement by Puppet.
Malware scan results
The malware detection service on Puppet Forge is an automated process that identifies known malware in module releases before they’re published. It is not intended to replace your own virus scanning solution.
Learn more about malware scans- Module name:
- puppetlabs-puppet_operational_dashboards
- Module version:
- 0.2.0
- Scan initiated:
- March 10th 2022, 16:57:16
- Detections:
- 0 / 55
- Scan stats:
- 55 undetected
- 0 harmless
- 0 failures
- 0 timeouts
- 0 malicious
- 0 suspicious
- 16 unsupported
- Scan report:
- View the detailed scan report