Icon

Comments have been closed on this page. Please use AppMon & UEM Open Q & A forum for questions about this plugin.

Overview

 

The HPOO Action Plug-in will allow you to call the HPOO REST interface to execute a specified work flow. Just add Action to your desired dynaTrace incident.

Name and Version

HPOO Action Plugin

Compatible with

dynaTrace 5.x, 6.x

Author

Brian Perrault

License

dynaTrace BSD 

Support Level

Community Supported

Download

com.hpoo.runFlow_1.0.0.jar 

Screenshots

 

Installation

Import the plugin on the dynaTrace Server. For more details see Plugins

Once installed on the dynaTrace Server you can use the plugin as an action for your Incident. You need to switch to the Advanced Action Configuration. The plugin requires several properties to be configured. See the description of the properties in the section below

 

dynaTrace Plug-in configuration Options

  • HPOO Protocol – Choose either the unsecured HTTP or the secured HTTPS protocol to connect to the HPOO web service with.
  • HPOO URL – The main URL used to connect to HPOO.  (EX: hpoo.domain.com)
  • HPOO Port – The port used for connecting to the HPOO web service. (Default: 8444)
  • HPOO Flow Path – The directory path to the desired flow. (EX: Library/ServerTeam/)
  • HPOO Flow Name – The name of the HPPO flow to be run.
  • HPOO Username – The username of the user to execute the HPOO Flow.  This user must have execute access for the desired flow in the desired HPOO environment
  • HPOO Password – The password for the user that will be executing the HPOO Flow.
  • HPOO Flow Parameters – The parameters to pass to the HPOO flow.  Parameters should be added to the list in the format of “parameter=value” (EX: port=22) and separated by a line end.  Several values can be extracted from the incident.  To use these simply place the specified key into the value portion of the parameter list (EX: parameter={$host}).
    • {$host} – The Fully Qualified DNS for the server or URL that caused the incident to alert
    • {$guid} – The GUID string provided by dynaTrace to identify each individual incident. This can be used for talking with the dynaTrace REST interface
    • {$agent} – If the alert was generated from a dynaTrace instrumented application, this will provide the name of the application, otherwise this will return “”
    • {$incident} – The name of the incident that was tripped
    • {$startTime} – The time that the incident was tripped in dynaTrace
    • {$severity} – The severity of the incident as set in dynaTrace.  The 3 levels are Error, Warning, and Informational.
    • {$profile} – The name of the dynaTrace system profile that contains the incident
    • {$dynaTrace} – The URL for the dynaTrace server that tripped the alert.  This can be used for talking with the dynaTrace REST interface
    • {$instance} – If the dynaTrace measure is dynamic, this will contain the name of the dynamic instance (EX: drive name, network adapter name, service name)
    • {$instanceType} – If the dynaTrace measure is dynamic, this will contain the type of dynamic measure (EX: service, drive, interface, PID)
    • {$measureValue} – The value of the measure that caused the threshold to be breached
    • {$measureUnit} – The unit for the measure that caused the threshold to be breached
    • {$thresholdValue} – The value set on the threshold for the violated measure
    • {$incidentMessage} – The message from the incident details