/
opEvents Customising Table Columns

opEvents Customising Table Columns

Feature Description

This is an advanced feature that allows customers to modify the data presented in tables.  The default table content has been carefully selected based on Opmantek's numerous years of network management experience.  This said there are cases where customers would like to alter the table data to display information that is important to their organisation.  Most opEvents pages with table data can be customised to display different content.  This feature allows table columns to be removed or added as required.

If when following these steps the View that is being modified does not behave normally; remove the custom configuration file and normality should be restored.

 

Views That Support Custom Columns

  • Actions

  • Raw Logs

  • Archive Logs

  • Nodes

  • Summary Reports

  • Edit Nodes

  • Dashboard

  • Events

  • Event Context (Node Summary)

  • Event Context (Actions)

  • Event Context (Recent Events)

  • Escalations

Available Columns

Columns properties that may be added can found here:  opEvents Normalised Event Properties

Configuration

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

View

Configuration file

Actions

opEvents_action-log.json

Raw Logs

opEvents_raw-log.json

Archive Lo

opEvents_archive-log.json

Nodes

opEvents_node-log.json

Summary Reports

opEvents_summary-reports.json

Edit Nodes

opEvents_node-ip.json

Current Events- Current Events Table

opEvents_current-events.json

Current Events- Recent Events Table

opEvents_active-events.json

Events by Node (Dashboard)

opEvents_index_events.json

Events

opEvents_current-events.json

Escalations

opEvents_escalations.json

Event Context- Actions Table

opEvents_node-action-log.json

Event Context- Recent Events Table

opEvents_node-recent-events.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.

Caution!

Enable this feature with care. 

Future opEvents upgrades will need to be watched carefully as tables and event properties can change across versions.  Based on this an upgrade has the potential to break the functionality of a custom table configuration.  If this feature is enabled it is highly recommend to upgrade in a test environment prior to upgrading the production environment.

 

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.

Property Attributes

Each property that is added will require a set of attributes.  This is an example of the attributes that belong to the comment property.

See Table Schema Cell Types and Formatters for more cell types and formatters.

{ "name": "comment", "label": "Comment", "cell": "string", "search": false, "editable": false }

Attribute Descriptions

  • name:  Name of the event property (opEvents Normalised Event Properties)

  • label:  The column name that will render in the web page.

  • cell:  The cell type, usually this will be "string".  For other options please contact Firstwave Support

  • search: Always false

  • editable: Always false

Adding and Removing Columns

To remove a column simply remove the associated section from the applicable json file.  To add a column add a new section in the json file.  The column placement will be relative to the order it is put in the json file.

The example below is the opEvents_action-log.json file.  The version on the left is the default version.  The version on the right adds an Event ID column between the data and event columns, it also removes the comment column.

// VERSION=0.4.0 // VERSION=0.4.0 [ [ { { "name": "date", "name": "date", "label": "Date", "label": "Date", "search": false, "search": false, "cell": "string", "cell": "string", "direction": "descending", "direction": "descending", "editable": false "editable": false }, }, { { "name": "event", "name": "eventid", "label": "Event", "label": "Event ID", "cell": "string", "cell": "string", "search": false, "search": false, "editable": false, "editable": false "cell": "LookupUrl", "replace_name": "id", }, "base_url_stash_key": "event_base_url" { }, "name": "event", { "label": "Event", "name": "node", "cell": "string", "label": "Node", "search": false, "search": false, "editable": false, "editable": false, "cell": "LookupUrl", "cell": "LookupUrl", "replace_name": "id", "base_url_stash_key": "node_base_url" "base_url_stash_key": "event_base_url" }, }, { { "name": "action", "name": "node", "label": "Action", "label": "Node", "cell": "string", "search": false, "search": false, "editable": false, "editable": false "cell": "LookupUrl", }, "base_url_stash_key": "node_base_url" { }, "name": "details", { "label": "Details", "name": "action", "cell": "string", "label": "Action", "editable": false "search": false, }, "editable": false { }, "name": "comment", { "label": "Comment", "name": "details", "cell": "string", "label": "Details", "search": false, "cell": "string", "editable": false "search": false, } "editable": false ] } ]

 

For example, the image below shows the default menu bar for the Actions view in opEvents.

After editing the opEvents_action-log.json file the extra column was added to the end of the row labeled "New Custom Column". This process can be replicated to display custom information in as many columns as you would like on this page.

Verification

It is not necessary to restart any daemons.  After editing the associated json file simply load (or reload) the view in question.  

 

Example: Adding Searchable Group and Location Columns to the Events Console

In the he opEvents console (the active_events page) shows two separate tables, each driven by its own schema file:

Table on the page

Schema file

Table on the page

Schema file

Current Events

opEvents_active-events.json

Recent Events

opEvents_current-events.json

The node's group and location are not part of a raw event, so they must first be copied onto events at creation time using opevents_event_copy_node_properties (the shipped default already copies configuration.group and configuration.location). Only events created after that option is set will carry the values.

Once events carry the data, decide which table you want the columns on - the Current Events table, the Recent Events table, or both - and add the column definitions to the matching schema file(s) in /usr/local/omk/conf/table_schemas/. You will find the orginal files to copy in /usr/local/omk/lib/json/opEvents/table_schemas/ The same two column objects work in either file.

Reference the copied properties by their underscore names (nodeinfo.configuration_group, nodeinfo.configuration_location) and set search to iregex to make each column searchable:

{ "name": "nodeinfo.configuration_group", "label": "Group", "cell": "string", "search": "iregex", "editable": false }, { "name": "nodeinfo.configuration_location", "label": "Location", "cell": "string", "search": "iregex", "editable": false }

Place these objects in the array in the position you want the columns to appear (columns render left to right in array order). The search value iregex renders a case-insensitive search box on the column; use true instead for an exact-match search.

After saving the file(s), restart the FirstWave Webserver (the omkd service) and reload the page:

sudo service omkd restart

Event Context Panel

The Event Context Panel has some default properties and some customisable properties, by default the following are displayed:

  • Authority (only displayed if event contains data in the authority and location field)

  • Time

  • Node Summary Table (see Node Summary Table Customisation)

  • Event Status (see Event Status Customisation)

  • Related Events

  • Event

  • Details

  • Priority

  • Last Updated

  • Escalation

Additional properties can be displayed as well.

By default the Event Context Panel will look like this, providing essential contextual information about the event.

Node Summary Table Configuration

In the Event Context Panel there are two customisable lists for displaying extra data, the first is the Node Summary List, which is the horizontal list and the Event Properties which is the vertical list, asillustrated in screenshot.  The Event Status can also be configured which is described below.

To change which node properties are displayed you can modify opevents_gui_event_node_summary_list config option in opCommon.json

By default these properties are displayed in the gui, any changes will require the omkd daemon to be restarted.  If the node has any notes, these will also be displayed.

"opevents_gui_event_node_summary_list" : ["configuration.businessService","configuration.customer","configuration.group","configuration.host","configuration.location","name"]

Additional Event Context Items

To display or change the additional event properties, modify opevents_gui_event_context_summary_list in opCommon.json change the properties as required.

 

By default no additional properties are displayed, to include them just add them to the array as below, any changes will require the omkd daemon to be restarted.

"opevents_gui_event_context_summary_list" : [ "stateful", "type" ],

Event Status Configuration

To provide support for event management workflows, opEvents includes the ability to define the event status, because almost all operational teams will have a slightly different event status, this is completely configurable.  The Event Status feature makes opEvents into a Technical Service Desk, which is a service desk for the technical teams to use, while your Service Desk is where your customers and users will open tickets.

When an engineer or operator receives the event, they would acknowledge the event to stop the escalations and automated actions and update the Event Status with where they are in the process of managing the event.  Every time the Event Status is changed this is logged into the event for tracking activities, audit trials and possibly Service Level Agreements.

First enable the feature by changing opevents_event_status_enabled  : 'true' in opCommon.json

"opevents_event_status_enabled" : "true",

Values which the operator can select are defined in opevents_event_status_values in opCommon.json, if enabled or the event has the status property, a select box will be rendered in the event context panel.

To configure to work for your team, decide on what fields you want to include in your status, we include the following:

"opevents_event_status_values" : [ { "status" : "Investigating" }, { "status" : "Resolved" } ],

By default, no value is set in the event, if you require a value to be set, you just update opevents_event_status_default_value in opCommon.json and restart both the FirstWave Webserver and the opEvents daemon:

sudo service omkd restart sudo service opeventsd restart
"opevents_event_status_default_value": "Detected",

Restarting Daemons

Restart the FirstWave Webserver (omkd, for the GUI)

sudo service omkd restart

Restart the opEvents Daemon which Processes Events.

sudo service opeventsd restart