<aside> 💡 Will come back later for this. No need for me atm
</aside>
Learn how to make your infrastructure reactive and self-healing using events and the reactor in Salt
Events are an integral part of almost everything Salt does. However, for the most part, these events are designed to be invisible and are designed to work behind the scenes to provide inter process communication and make a complex system feel simple and friendly to the user.
We can also leverage the event system for our own purposes.
To see which events are currently happening in your system, the state.event is provided for this purpose. If we run it with no arguments, it will automatically connect to the master event bus and print all events that come through that bus.
If no jobs are active, the easy way to test the state.event function is to run a job such as test.ping
If you look at the first event in the output, you can see that an event was fired when a new job was created. The event data contains the function that is being run (test.ping) as well as the arguments for that function, the minions on which the function will run, and so on. Events formatted like the second event in the output are fired whenever a minion reauthenticates with the master. This can happen under a variety of circumstances, so you will see these types of events frequently on the event bus.