Forge Home

Modules

Puppet

Resources

PuppetEcosystemPuppet CommunityUpdates

self_service

A Puppet Enterprise Module to Promote Preventative Maintenance and Self Service
Project URLRSS FeedReport issues

1,033 downloads

665 latest version

5.0 quality score

We run a couple of automated
scans to help you access a
module's quality. Each module is
given a score based on how well
the author has formatted their
code and documentation and
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.

Version information

  • 0.2.0 (latest)
  • 0.1.0
released Jan 11th 2022
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
  • Puppet >= 6.16.0 < 8.0.0
  • , , , , ,
This module has been deprecated by its author since Feb 16th 2022.

The author has suggested puppetlabs-pe_status_check as its replacement.

Start using this module

Documentation

puppetlabs/self_service — version 0.2.0 Jan 11th 2022

puppetlabs-self_service

  1. Description
  2. Setup - The basics of getting started with self_service
  3. Usage - Configuration options and additional functionality
  4. Reference - what to do when a indicator repors a fault
  5. Limitations - OS compatibility, etc.
  6. Development - Guide for contributing to the module

Description

puppetlabs-self_service aims to provide a mechnism to alert the end-user when Puppet Enterprise is not in an ideal state. It uses pre-set indicators and has a simplified output that directs the end-user to next steps for resolution.

Users of the tool should expect greater ability to provide the self served resolutions, as well as shorter incident resolution times with Puppet Enterprise Support due to higher quality information available to support cases.

Setup

What self_service affects

This module installs a structured fact named self_service, which contains an array of key pairs tha simply output an indicator ID and a boolean value.

Setup Requirements

Plugin-Sync should be enabled to deliver the facts this module requires

Beginning with self_service

puppetlabs-self_service primarly provides the indicators by means of facts so installing the module and allowing plugin sync to occur will allow the module to start functioning

Usage

The Facts contained in this module can be used for direct consumption by monitoring tools such as Splunk, any element in the structured fact self_service reporting as "false" indicates a fault state in Puppet Enterprise. When any of the elements reports as false, the incident ID should be looked up in the reference section for next steps

Alternativly assigning the class self_service to the infrastructure Will "Notify" on Each Puppet run if any of the indicators are in a fault state.

Class Delcaration Optional.

To activate the notification functions of this module, classify your Puppet Infrastructure with the self_service class using your preferred classification method. Below is an example using site.pp.

node 'node.example.com' {
  include self_service
}

While the entirity of the default indictors should be reported on for maximum coverage, it may be nessary to make exceptions for your particular environment. to do this classify the array parameter indicator_exclusions with an list of all indicators you do not want to report on.

class { 'self_service':
  indicator_exclusions             => ['S0001','S0003','S0003','S0004'],
}

Reference

This section should be referred to for next steps when any indicator reports a fault

Indicator ID Description Self Service Steps What to Include in a Support Ticket
S0001 Determines if Puppet agent Service is running Start the puppet agent - puppet resource service puppet ensure=running If the Puppet agent fails to start with the self service step raise a support case quoting reference S0001 and providing syslog and any error output when attempting to restart the service
S0002 Determines if pxp-agent Service is running Start the pxp-agent - puppet resource service pxp-agent ensure=running If the Pxp-agent fails to start with the self service step raise a support case quoting reference S0002 and providing syslog, any error output when attempting to restart the service and /var/log/puppetlabs/pxp-agent/pxp-agent.log
S0003 Determines if Infrastructure components are running in NOOP Noop should not be routinely configured on PE infrastructure nodes as it prevents the management of key infrastructure settings. Please disable this setting on any infrastructure component https://puppet.com/docs/puppet/7/configuration.html#noop If you are unable, or encounter an error when disabling noop, raise a support case quoting reference S0002 and any errors output when attempting to change the setting
S0004 Determines if infrastructure status is not green Run the command puppet infrastructure status on your primary node, note any services showing in an error state and examine the corresponding service logs for potential causes Raise a support case quoting reference S0004 along with the output of puppet infrastructure status and any service logs associated with the errors
S0005 Determines if CA expires within 90 days Install the following module https://forge.puppet.com/modules/puppetlabs/ca_extend and follow the documentation to extend the CA Raise a support case quoting reference S0005 together with the support script output from the primary node, and any errors encountered when using the ca_extend module
S0006 Determines if 15m Load Average is greater than available cores A 15m Load Average greater than the number of cores, indicates system over capacity, it should be determined if Puppet Enterprise processes are using the CPU and if so commonly issues of capacity and tuning are at fault. Metrics can be used to pinpoint the issue https://support.puppet.com/hc/en-us/articles/231751308-Troubleshoot-and-fix-performance-issues-with-the-puppetlabs-puppet-metrics-collector-module-in-Puppet-Enterprise-2016-4-to-2019-8-and-2021-1 Raise a support case quoting reference S0006 detailing the Puppet process(es) consuming CPU, and a full support script from the node in question along with any findings from metrics analysis
S0007 Determines if there is at least 20% disk free on postgres Data partition Determine if the growth is slow and expected within the TTL of your data, unexpected increase can be due to error states this article should be consulted https://support.puppet.com/hc/en-us/articles/360056219974-Troubleshoot-PuppetDB-pe-puppetdb-in-Puppet-Enterprise Raise a support case quoting reference S0007 detailing the files and folders and rate of growth, along with a full support script from the node in question
S0008 Determines if there is at least 20% disk free on the Codedir Data Partition This can indicate you are deploying more code from the code repo than there is space for on the infrastructure components, or something else is consuming space on this partition. Check the mount that the directory indicated by puppet config print codedir resides has enough capacity for the code being deployed, and check no other outside files are consuming this data mount
S0009 Determines if Pe-puppetsever Service is Running and Enabled on relevant components Check the Service can be started and enabled puppet resource service pe-puppetserver ensure=running examing /var/log/puppetlabs/puppetserver/puppetserver.log for failures Raise a support case quoting reference S0009 along with the log below, showing an unsuccessful startup /var/log/puppetlabs/puppetserver/puppetserver.log
S0010 Determines if Pe-puppetdb Service is Running and Enabled on relevant components Check the Service can be started and enabled puppet resource service pe-pupeptdb ensure=running examing /var/log/puppetlabs/puppetdb/puppetdb.log for failures Raise a support case quoting reference S0010 along with the log below, showing an unsuccessful startup /var/log/puppetlabs/puppetdb/puppetdb.log
S0011 Determines if Pe-postgres Service is Running and Enabled on relevant components Check the Service can be started and enabled puppet resource service pe-postgres ensure=running examing /var/log/puppetlabs/postgresql//postgresql-.log for failures Raise a support case quoting reference S0011 along with the log below, showing an unsuccessful startup /var/log/puppetlabs/postgresql// postgresql-.log
S0012 Determines if Puppet produced a report within the last run interval https://puppet.com/docs/pe/2021.4/run_puppet_on_nodes.html#troubleshooting_puppet_run_failures Raise a support case quoting reference S0012 along with the output of puppet agent -td > debug.log 2>&1
S0013 Determines if a catalog successfully applied on Puppet Agent Last run https://puppet.com/docs/pe/2021.4/run_puppet_on_nodes.html#troubleshooting_puppet_run_failures Raise a support case quoting reference S0013 along with the output of puppet agent -td > debug.log 2>&1

Limitations

Development