...
Columns properties that may be added can found here: opEvents Normalised Event Properties
Configuration
Enabling the Feature
In order to enable this feature a directory must be copied into the standard omk config directory.
| Code Block |
|---|
[root@opmantek ~]# cp -r /usr/local/omk/lib/json/opEvents/table_schemas/ /usr/local/omk/conf/. |
Configuration Files
Each view has a separate configuration file that may be found in the following directory:
/usr/local/omk/conf/table_schemas
Configuration Files
Each view has a separate configuration file that will be found in the following directory (by default this directory does not exist; reference the next step):
/usr/local/omk/conf/table_schemas
| View | Configuration file |
|---|---|
| Actions | opEvents_action-log.json |
| Raw Logs | opEvents_raw-log.json |
| Archive Logs | opEvents_archive-log.json |
| Nodes | opEvents_node-log.json |
| Summary Reports | opEvents_summary-reports.json |
| Edit | |
| View | Configuration file |
| Actions | opEvents_action-log.json |
| Raw Logs | opEvents_raw-log.json |
| Archive Logs | opEvents_archive-log.json |
| Nodes | opEvents_node- | log.json
| Summary Reports | opEvents_summary-reports.json | Edit Nodes | opEvents_node-ip.json
| ip.json |
Enabling the Feature
In order to enable this feature the following must be done.
- Create a directory called /usr/local/omk/conf/table_schemas
- Copy the specific view configuration file that requires modification from /usr/local/omk/lib/json/opEvents/table_schemas/ into /usr/local/omk/conf/table_schemas.
- Only the necessary json files should be copied to the /usr/local/omk/conf/table_schemas directory as having unecessary config files in this directory will result in future upgrades being unpredictable.
Configuration
The configuration files are json files that have a specific syntax that must be observed. Add the desired property to the json file in the order it should appear in. The table will be constructed left to right based on attributed that are read from the top down.
...