Introduction
Remediate reduces the risk of external attacks and data breaches by offering visibility into your infrastructure as well as the capabilities to prioritize and take action in events. You can use Remediate to reduce the repetitive and error-prone stages of manual data which are handover between teams.
In this article, we will discuss the Puppet remediate, latest events, discovery events, and tasks events in detail.
Events in Puppet Remediate
The events in puppet remediate help in reducing the risk of outside attacks and data breaches. An event takes action by giving you insight into the risks present across your system.
Latest Events
It shows the list of the latest events of puppet remediate. We will discuss the latest events individually with the date and time to find when the event fails or succeeds.
The Latest events metrics bar of puppet remediate discusses the total number of
🔻discovery runs
🔻task runs
| Latest Events | Description |
| Status |
The status of each event may come under the following property: 🔻Succeded 🔻Failed 🔻Pending 🔻Running |
| Started by | It describes the name of the user who has started the event. |
| Submission time | It describes the time taken to submit the event. Submission time can be within a month, day or year. |
We will discuss the type of event in detail in the below section.
Discovery events
Discovery events provide information about
🔻The total number of jobs created as a result of the discovery event. Each discovery event has two functions:
▶️Discover a node.
▶️Discover resources on a node.
🔻The failed number of jobs.
🔻The status of the latest task event.
🔻Information about the person who initiated the last task run event.
🔻The date and time the task run event started.
The discovery event table in puppet remediate gives us the information about
| Events | Description |
| Status |
The status of each event may come under the following property 🔻Succeded 🔻Failed 🔻Pending 🔻Running |
| Started by | It describes the name of the user who has started the event. |
| Submission time | It describes the time taken to submit the event. Submission time can be within a month, day or year. |
| Source | It can be of two types: vulnerability scanner or infrastructure source. |
| Job details |
It provides information on the job which confirms the successful discovery or reason for a failure:
🔻Successfully connected: It denotes that remediate was able to connect to the node and retrieve data on a set of facets (packages and/or containers). 🔻Unable to connect: It denotes that remediate was not able to reach a specified event. 🔻No valid credentials available: It denotes that remediate was able to connect to a node but did not have valid credentials for any further discovery. |
Tasks events
Tasks events provide information about
🔻The total number of jobs created as a result of the task event. Each task event has two functions:
▶️Run the tasks on a node.
▶️Discover the resources on a node.
🔻The failed total number of jobs.
🔻The status of the latest task event.
🔻Information about the person who initiated the last task run event.
🔻The date and time the task run event started.
The task event table in puppet remediate gives us the information about
| Events | Description |
| Status |
The status of each event may come under 🔻Succeded 🔻Failed 🔻Pending 🔻Running |
| Submission time | It describes the time taken to submit the event. Submission time can be within a month, day or year. |
| Source | It can be of two types: vulnerability scanner or infrastructure source. |
| Job details | It describes the task's command output and the number of facets discovered. Each facet represents a collection of linked attributes, that are independently maintained, that characterize a specific element of a discovered resource, such as a node, package, or container. |
34+ registered 
