LANDesk Ticket Integration- Node Down Alert to Incident

Version 1

                                                                                                   Convert Solarwinds node down alerts as incidents in LANDesk


    This alert will convert all Node Windows server Alerts as tickets in LANDesk, These action will trigger an Event to LANDesk and then the events will be processed as Incident. Once the server is up. It will automatically send an Up event and update the information in the respective tickets. 


    Modify the trigger and reset condition as required for windows servers,Network devices etc.. Same way you can create tickets for High CPU, Memory, Disk Space etc..


    Requirements in LANDesk:


    Your LANDesk system should have the below requirements,

    • Postevent should be enabled
    • Create a new source for Solarwinds Alert as Solarwinds
    • Map your custom properties versus parameters in Landesk (This is very critical to pass the right information in LANDesk)
    • All the down events will be posted as Alert
    • All the respectove up events will be posted as UP
    • you can have n number of custom properties mapped to parameter in LAndesk.
    • Copy the postevent.exe in Solarwinds polling Engine
    • Export all the node details from Solarwinds and update in LAndesk CMDB(I have automted script which does that from LANDesk to Solarwinds which I will share later)
    • Parameters mentioned below is an example you can customize as reuired.


    LANDesk Post event Command

    In order to execute this integration, Event management tool has to be Configured so that it sends a command line string to call an executable file as follows

    PostEvent "<Event Source>" "<Event Type>" "<Event Title>" "[<Description>]" "[<Configuration Item>]" "[<Priority>]" "[<Status>]" "[<Parameter1>]" "[<Parameter2>]" "[<Parameter3>]"


    Command used in Solarwinds alert configuration


    Trigger action command


    D:\DND\PostEvent.exe SolarWinds Alert "CRITICAL ALERT ${N=SwisEntity;M=Caption} is  ${N=SwisEntity;M=Status}" "CRITICAL ALERT ${N=SwisEntity;M=Caption} is ${N=SwisEntity;M=Status} in ${N=SwisEntity;M=CustomProperties.Region}       IP Address ${N=SwisEntity;M=IP_Address}" ${N=SwisEntity;M=Caption} "" "" "" "" "NOC Support" "${N=SwisEntity;M=CustomProperties.CustomerName}" Device


    Reset Action command


    D:\DND\PostEvent.exe SolarWinds UP "${N=SwisEntity;M=Caption} is ${N=SwisEntity;M=Status}" "${N=SwisEntity;M=Caption} is ${N=SwisEntity;M=Status} in ${N=SwisEntity;M=CustomProperties.Region}       IP Address    ${N=SwisEntity;M=IP_Address}" ${N=SwisEntity;M=Caption} "" "" "" "" "NOC Support" "${N=SwisEntity;M=CustomProperties.CustomerName}" Device



    You can have any custom properties in these. Mapping the rite parameters is important for this to work.