By default opEvents ships with the standard color pallet of a green event status being good, a yellow meaning something needs to be addressed or is starting to degrade, and red being a critical event. This color scheme will work in most cases however, Opmantek understands one size does not fit all. You can edit the event colors based on priority levels and it is as simple as editing a small line in a single file.
Changing event colors based on priority can be accomplished by following these six steps:
1. Find the hex color you want to use through google or some other site.
2. Navigate to /usr/local/omk/public/omk/css
| Code Block |
|---|
cd /usr/local/omk/public/omk/css |
3. Edit the opEvents_b_internal_packed.css file
| Code Block |
|---|
vi opEvents_b_internal_packed.css |
4. In this file you can see the priority levels as well as the associated color code. i.e event_priority_2{background-color:#59cf59. You would simply replace the current color codes with the one you’d like to use then save the file. It’s recommended to create a backup before making any changes.
5. Restart the opevents and omk daemons:
| Code Block |
|---|
service opeventsd restart service omkd restart |
6. You may also need to restart and clear out your browser cache and cookies for the changes to display.
Once the services are restarted and the browser is refreshed and cache cleared, you will see the new color of the priority levels that you set change. That's all there is to it.
...