Foglight Evolve 9.2 - Creating Actions Field Guide

Adding Custom Action Types to Foglight

This Creating Actions Field Guide provides conceptual information about actions in Foglight®, along with configuration and instructions that will help you create custom action types.

This guide is intended for Foglight cartridge developers and field engineers who need to create actions in Foglight.

About Foglight Actions

Foglight® actions are building blocks that can be bound to rules. Actions can interact with other systems, run scripts or manipulate the environment in other ways when a rule condition to which the action is bound to is met. A default Foglight installation contains a collection of core action types that you can bind to rules as required. They include email actions, command-type actions, script actions, and others. For complete information about core actions and how to add them to rule definitions, see the Administration and Configuration Guide.

In monitoring environments where the functionality of core Foglight actions does not meet the needs of your business requirements, you can create custom action types and add them to Foglight as required. This guide is packaged with a ZIP file, Foglight_5.9.x_CreatingActionsFieldGuide.zip. Use this file as a template when creating custom action types.

NOTE: The file CreatingActions_FieldGuide.zip is packaged with this guide on the Quest Technical Documentation page, http://documents.quest.com. You can download it from the Support Portal: https://support.quest.com/

Getting Started

Before you get started with writing the code for custom actions, you need to ensure that your development environment includes the tools you need, create a valid directory structure, and ensure that the appropriate environment variables exist and point to the correct locations on your system. For complete information, see the following sections:

What You Need

First thing you need to do is to ensure that your development machine has all of the required tools needed to proceed with writing and building your code. The following list identifies the required software components: