Refer below for next steps when any indicator reports a false. This fact is confined to run on infrastructure nodes only. The node is a certificate authority but not a postgres hostĪ failure to determine node type will result in a safe subset of checks being run that will work on all infrastructure node types. The node has the master role but not the puppetdb role The node has both the master and puppetdb roles The node has the primary_master_replica role The node is both a certificate authority and a postgres host The fact queries which Puppet Enterprise Roles have been classified to each node and uses this to make the determination. This fact is used to determine which individual status checks should be run on each individual infrastructure node. node '' ' Reference Fact: pe_status_check_role To activate the notification functions of this module, classify your Puppet Infrastructure with the pe_status_check class using your preferred classification method. Pe_status_check::agent_status_enable::agent_status_enabled = false Reporting Options Class declaration pe_status_check (optional) Disabling agent_status_checkįollowing the addition of the class pe_status_check::agent_status_enable to an agent node, disable the collection of agent_status_check fact, set the following parameter: Enabling agent_status_checkīy default your normal agent population will not collect the agent_status_check fact, this can be enabled for all agents or a subset of agents, by classifying pe_status_check::agent_status_enable to your nodes. When any element reports as false, look up the incident ID in the reference section for next steps.Īlternatively, assigning the class pe_status_check to the infrastructure notifies on each Puppet run if any indicator is reporting as false, this can be viewed in the Puppet report for each node. The facts in this module can be directly consumed by monitoring tools such as Splunk, any element in the structured facts pe_status_check or agent_status_check reporting as false indicates a fault state in Puppet Enterprise. This module primarily provides indicators using facts, so installing the module and allowing plug-in sync to occur lets the module start functioning.Ĭollection of the agent_status_check fact is disabled by default so as not to affect all puppet agents indiscriminately Usage Install the module, plug-in sync will be used to deliver the required facts for this module, to each agent node in the environment the module is installed in. The pe_status_check fact is confined to only Puppet Enterprise infrastructure agents, and the agent_status_check fact is confined to non-infrastructure agent nodes. Each fact contains an array of key pairs that output an indicator ID and a Boolean value. This module installs two structured facts named pe_status_check and agent_status_check. Users of the tool have a greater ability to provide their own self-service resolutions and shorter incident resolution times with Puppet Support due to higher quality information available to our team. It uses pre-set indicators and has a simplified output that directs the end-user to the next steps for resolution. Puppetlabs-pe_status_check provides a way to alert the end-user when Puppet Enterprise is not in an ideal state. How to report an issue or contribute to the module.Class declaration pe_status_check (optional).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |