opEventsships with a lot of features but what is ships with is not all that it can do. Opmantek's various modules are meant to be tinkered with to give you a product that works specifically for you. With a little thought and planning you and your team can make opCharts and other Opmantek modules act as if they were made custom for your organization.

Thought process

So opEvents is set up and running and you are able to see every event that is occurring. You are happy knowing any time an event pops up you can clearly see it as well as dig into the event details but there is still work to be done once the event occurs. You notice one event in particular, high bandwidth usage keeps displaying in the event list and you keep having to run the same few commands every time to troubleshoot and resolve the issue. You remember that opConfig allows for command

power point slides step 1 do this step 2 do that.

asgard link in edit node - /omk/opCharts/nodes/$node_name/resources/interface creates a link

create a page, start with outline, ask why is this important. Why does customer care? How can bridge gap from where they are now to great things. four step process in the videos. start by identifying a simple event you deal with often and what are steps engineer takes to troubleshoot it and what are steps to fix it and how can automate steps to troubleshoot. focus on idea on troubleshooting then remediation.

opevents, event actions. dual purpose for events and config possibly. dont get into building an event action, theory of troubleshooting steps I want to take to create event actions. what commands want to run on devices.

how do a understand wha commands are htere now b identify what things they want to collect in their environment. might ship with mtr as a command but dont want to use that one. customize it to your needs.