Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://www.puppet.com/blog/event-driven-automation below:

What is Event-Driven Automation? Event-Driven Automation Programming Examples

Event-driven automation can turn repetitive, manual, daily tasks into something that you set and forget. It’s a great way to trigger automatic events and prevent human error.

In this blog, we'll explore a few event-driven automation programming examples, from sending an email to a certain group of users when a file has been uploaded to a server to generating reports.

Table of Contents: 

• What is Event-Driven Automation?
• Exploring the Benefits of Event-Driven Automation
• Event-Driven Automation Programming Examples
• Hardening Security and Compliance with Event-Driven Automation
• Using Puppet as Part of Event-Driven Automation Workflows 

Event-driven automation is a programming automation that reacts to triggers like tickets, incidents, Git events, changes in system state, and more. When an event is detected, event-driven automation initiates scripts, workflows, and more response mechanisms.

Event-driven automation is really one piece of a larger IT automation strategy. The goal of event-driven automation is to minimize manual interference and improve scalability and overall compliance.

An event that triggers an action within a system can come from locations and other services like: 

• Cloud events
• Git events
• Incidents
• Tickets
• Monitoring 

The response to any event from one of these services can be customized according to need. For example, if there is a security or a compliance breach, an instance could be automatically shut down while it waits for analysis. 

Events can also trigger communications to an individual or team. If a security breach is detected, for example, this can be shared via Slack or Microsoft Teams for instance to raise the alarm. 

The most important piece of event-driven IT automation is that it works within the provider tools and application programming interfaces (APIs) that your system is already using. Ideally, this automation can trigger responses across different tools and services to ensure that everything is working in harmony. 

There are three main parts to an event-driven response: 

• The Event: Something occurs within a particular system or service to trigger an event.
• The Action: The pre-defined action is triggered and deployed as planned ahead of time.
• The Result: A communication, report, or analysis is sent to notify the relevant team members that the event-driven response took place. 

The benefits of event-driven automation overlap with those of automation in general. It’s a function that you don’t have to think about or actively manage in order to see the benefits. 

• Enhanced Security and Compliance: Proactively planning a response to a breach, an incident, or even an unwanted login can help you strengthen your compliance and security goals.
• Enhanced Accuracy and Efficiency: Manual work cuts in two ways: it eats up valuable time and introduces a risk of error.
• Enhanced Scalability: Need to add fifty new users to your system? It’s not a problem when you’ve already set up a strong series of event-driven automations to handle actions users might take or problems they might encounter in the future. 

Examples of event-driven automation include automatic resource scaling, logging, alerts, remediation, and more in response to specific events in a system.

Heading back to our formula of Event > Action > Result, let’s look at a common example of a system outage within an organization.

We’ll say that in this example company operates a call center where it’s business critical for the computer system to function for the support technicians to help out customers. 

• The Event: At one of the call center locations, an individual system outage is detected by a monitoring tool that is connected to the larger system. This outage is impacting one particular physical location.
• The Action: Within the system, an automated script is triggered to collect data about the outage, such as the time it started, the affected systems, and the error messages. This is the set action that was planned previously to make sure that outages receive a quick response.
• The Result: The information gathered during the “action” phase is sent to a team of engineers who can use it to troubleshoot the outage and restore the system. They can also use this information to re-route call volume if necessary and spare customers unnecessary wait times.

Security incidents don’t wait for you to get ready for them. They happen when your IT team is already putting out fires, prepping for audits, trying to roll out updates, and so much more.

Event-driven automation can help harden IT systems to make sure that when security-related incidents do happen, like compliance drift or a tool like Splunk reports an issue, then the event-drive response can be triggered to either alert your team or put a different API into action. 

Here are a few examples how event-driven automation can harden your overall security strategy: 

• Detect and Respond to Unauthorized Access: If an unauthorized login attempt is detected, the event-driven automation system can stop the attempt and let the security team know the details of what happened.
• Apply Security Patches: Event-driven automation can be used to automatically apply security patches to systems and applications. This can help to reduce the risk of vulnerabilities across different types of software and devices.
• Monitor for Suspicious Activity: Event-driven automation can monitor for suspicious activity, such as unusual login patterns or data exfiltration. If suspicious activity is detected, the event-driven automation system can automatically alert the security team. 

The role in helping with event-driven workflows isn’t a new feature or function within Puppet — it’s been a part of the Puppet DNA since the very beginning.

Puppet’s implementation of APIs is agnostic, which means that it works with all of the other software programs you’re already using. An example of this would be ServiceNow, where there is a plugin to connect to Puppet through an API to execute an appropriate automated orchestration and complete a workflow, whether there is a human on the other end. 

There are modules within the Puppet Forge that can start, stop, or restart a service like a web server. The Puppet API interface places the actions for event-driven workflows in a platform designed and driven for configuration management actions. When an event is detected through any third-party system that the web server has an issue, Puppet acts as the action engine with an appropriate orchestrated response. For instance, the event monitoring system can call the Puppet API orchestration interface in the event of an outage, and have Puppet restart the server automatically. Once completed, the orchestration within Puppet can notify the event monitoring system the server is back online. 

One of our customers uses Puppet to provision their server. They use an API to automate the process of provisioning, which in turn calls on Puppet to complete the provisioning steps once the automation is complete. It’s a one-two step process that is completely managed through event-driven automation, saving their team valuable time. 

Put Puppet to work in your infrastructures event-driven automation workflows — test out a free trial of Puppet to see it in action:

Put Puppet’s event-driven automation to work in your infrastructure with a free trial:

TRY PUPPET FOR EVENT-DRIVEN AUTOMATION

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4