• 1 Minute to read
  • Contributors
  • Dark
  • PDF


  • Dark
  • PDF


Data present in DNIF modules for an incident can be pushed into the Everest ITSM queue to take action upon

Pre-requisites to use Everest and DNIF

Outbound access required for connectivity between DNIF Setup and Everest queue.

Protocol Source IP Source Port Direction Destination IP Destination Port
TCP DS,CR Any Egress Everest_IP Everest_PORT

The above rule assumes both request and response in enabled

Everest trigger plugin functions

Details of the function that can be used with the Everest trigger is given in this section.

  • create_ticket

This function allows for data present in the data stack after raising a module to be pushed into the Everest ITSM .

  • Input
    Custom message to be pushed to Everest ITSM as summary

The message has to be present between double quotes("")

The fields $category, $categoryName, $service, $serviceName are fields which are required to be added to DNIF data stack to create a ticket in Everest ITSM.
For more details on available values $category,$categoryName,$service,$serviceName refer to the supplied service catalouge json of everest


_fetch $DevSrcIP from event limit 1
>>_raise module <package_slug> <module_slug> $DevSrcIP 5 5m
>>_field $category string "11"
>>_field $categoryName string "Everest"
>>_field $service string "11"
>>_field $serviceName string "everest"
>> _trigger api everest create_ticket "CustomeName:Sev _Severity_ : _Name_ for _EvtName_ of _EvtType_"

The _ Field_ is replaced with actual value of $Field present in data stack



The output of the trigger call has the following structure (for the available data)

Field Description
$EverestStatus Status of ticket creation (success/fail)
$EverestMessage Success/failure status message for ticket creation
$EveresDisplayID ID being displayed to user for incident creation
$EverestID Incident ID in everest

Using the Everest ITSM API and DNIF

Getting started with Everest ITSM API and DNIF

  • Place the everest.tar.gz in the /var/tmp location of host machine.
  • Login to your Data Store, Correlator containers, access DNIF Container via SSH
  • Copy the files on the server from location /var/tmp to the relevant location using below commands:
cp /var/tmp/everest.tar.gz /dnif/<D-key>/trigger_plugins/
  • Move to the ‘/dnif/<D-Key>/trigger_plugins’ folder path.
cd /dnif/<D-Key>/trigger_plugins/
  • Extract the everest.tar.gz using the following command
tar -xvzf everest.tar.gz
  • Move to the ‘/dnif/<D-key>/trigger_plugins/everest/’ folder path and edit the dnifconfig.yml configuration file
  • Replace the tag:<Add_your_Everest_*> with your Everest credentials
  EVEREST_USERID: <Add_your_Everest_UserID>
  EVEREST_PASS: <Add_your_Everest_Password>
  EVEREST_URL: <Add_your_Everest_Password example http(s)://1x.xx.xx.xx:80>
  EVEREST_REQUESTER_EMAIL: <Add_your_Everest_Requester_EmailID>
  EVEREST_REQUESTER_NAME: <Add_your_Everest_Requester_Name>
  EVEREST_REQUESTER_MOBILE: <Add_your_Everest_Requester_Mobile>

Was this article helpful?

What's Next