Moogsoft - GermainUX Docs

ComponentsEngine

Availability2014.1 or later

Integrate GermainUX Alerts with Moogsoft

Sending alerts over HTTP

Create a Custom Integration in Moogsoft

Setting up the endpoint

Recommended Event Fields

Context for responders

Security and Operational Considerations

Credentials and operating safeguards

Integrate GermainUX Alerts with Moogsoft

GermainUX can send real-time alerts and events to Moogsoft APEX AIOps Incident Management through an HTTP Action. The integration helps operations teams detect, correlate, prioritize, and resolve issues by sending GermainUX SLA violations and other monitored conditions directly to Moogsoft.

Events can be sent:

When an SLA is breached
When a synthetic scenario fails
When a critical error or anomaly is detected
On a configured schedule
Through a manual execution

Create a Custom Integration in Moogsoft

If a custom inbound integration does not already exist:

Go to Integrations > Inbound Integrations > Create Your Own Integration

Select Add New Integration

Enter a unique integration name and optional description

Select Events as the data type

Save the integration

Copy the generated endpoint and obtain an API key

Configure the required event-field mappings and severity mappings

Validate and enable the integration

Moogsoft generates the custom endpoint for the integration. Use the exact endpoint and authentication method displayed in its Configuration Information section rather than constructing the URL manually. See Create Your Own Integration and Define a Custom Integration.

Create the GermainUX HTTP Action

Go to: GermainUX Workspace > Automation > HTTP Select the Add icon to open the HTTP Action wizard.

1 Step 1: Configure the Action

Enter the action settings:

Field	Example
Name	`Send Alert to Moogsoft`
Execution Count	`1`

Select Next.

2 Step 2: Configure the HTTP Request

Field	Value
Path	Custom integration endpoint generated by Moogsoft
Request Method	`POST`
Content Type	`application/json`
Expected Response	Successful status returned by the configured Moogsoft endpoint, typically a `2xx` response
Authentication	API key configured according to the Moogsoft integration instructions

Example Request Body

{
  "description": "GermainUX detected that SLA ${context.sla.name} was not met.",
  "severity": "<#if context.sla??>${5 - context.sla.severity.ordinal()}<#else>0</#if>",
  "source": "${context.fact.system.hostname}",
  "check": "GermainUX",
  "service": [
    "retail",
    "support"
  ],
  "tags": {
    "origin": "GermainUX"
  }
}

Adapt the payload and severity mapping to the fields configured in your Moogsoft custom integration.

Example Headers

Accept: application/json
Content-Type: application/json
apiKey: <MOOGSOFT_API_KEY>

Use the authentication format provided by Moogsoft for the specific integration. Moogsoft custom integrations support API-key-based authentication, including supported basic or bearer-token configurations. Store the API key in a protected GermainUX credential reference. Do not embed a production key directly in the action body, documentation, or exported configuration.

3 Step 3: Assign the Trigger

Configure when GermainUX should send the event. For example, to create a Moogsoft event when a synthetic scenario fails:

Select the synthetic-scenario KPI

Configure or select its failure SLA

Add the Moogsoft HTTP Action as the SLA Action

Save the SLA and action configuration

The same HTTP Action can be associated with other SLAs or automation conditions.

4 Step 4: Finish and Test

Complete the wizard

Run the HTTP Action manually

Confirm that GermainUX receives a successful HTTP response

Open the Moogsoft custom integration

Confirm that the test payload appears in Map Your Data

Map the incoming fields to the appropriate Moogsoft event fields

Validate and enable the integration

Force a controlled GermainUX SLA breach and confirm that a new Moogsoft event is created

Recommended Event Fields

GermainUX context	Moogsoft field
SLA or error description	`description`
GermainUX severity or priority	`severity`
Hostname, application, or monitored system	`source`
KPI, SLA, or check name	`check`
Application or business service	`service`
Environment, session, user impact, or dashboard link	`tags`

Include enough context for Moogsoft users to understand the issue and open the relevant GermainUX Analysis view.

Security and Operational Considerations

Store the Moogsoft API key as a protected credential.
Restrict access to users authorized to modify the HTTP Action.
Use HTTPS only.
Avoid sending unnecessary personal or sensitive data.
Configure retries and execution limits carefully.
Prevent duplicate incidents through Moogsoft deduplication and GermainUX Quiet Time.
Test severity mappings before production use.
Monitor failed HTTP executions and API-key expiration.

Get Help

Contact GermainUX Support

The Germain Team can help you set this up.

Can't find what you need?

Search all GermainUX docs with Ctrl + K, or use the feedback buttons at the bottom of this page to tell us what is missing.

The content of this document is proprietary to GERMAIN SOFTWARE LLC.

Integrate GermainUX Alerts with Moogsoft

Create a Custom Integration in Moogsoft

Recommended Event Fields

Security and Operational Considerations

​Integrate GermainUX Alerts with Moogsoft

​Create a Custom Integration in Moogsoft

​Create the GermainUX HTTP Action

​1 Step 1: Configure the Action

​2 Step 2: Configure the HTTP Request

​Example Request Body

​Example Headers

​3 Step 3: Assign the Trigger

​4 Step 4: Finish and Test

​Recommended Event Fields

​Security and Operational Considerations

​Get Help

Contact GermainUX Support

Can't find what you need?

Integrate GermainUX Alerts with Moogsoft

Create a Custom Integration in Moogsoft

Create the GermainUX HTTP Action

1 Step 1: Configure the Action

2 Step 2: Configure the HTTP Request

Example Request Body

Example Headers

3 Step 3: Assign the Trigger

4 Step 4: Finish and Test

Recommended Event Fields

Security and Operational Considerations

Get Help