> ## Documentation Index
> Fetch the complete documentation index at: https://docs.germainux.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Moogsoft

> GermainUX can send real-time alerts and events to Moogsoft APEX AIOps Incident Management through an HTTP Action.

Components
[`Engine`](https://docs.germainux.com/main/germain-ux-engine)

Availability
2014.1 or later

> **[Integrate GermainUX Alerts with Moogsoft](#integrate-germainux-alerts-with-moogsoft)**
>
> Sending alerts over HTTP

> **[Create a Custom Integration in Moogsoft](#create-a-custom-integration-in-moogsoft)**
>
> Setting up the endpoint

> **[Recommended Event Fields](#recommended-event-fields)**
>
> Context for responders

> **[Security and Operational Considerations](#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.

![Moogsoft: Integrate GermainUX Alerts with Moogsoft](https://mintcdn.com/germain-ux/ARpsBmsSl-QLchOO/images/main/moogsoft/image-20230717-210546.png?fit=max\&auto=format\&n=ARpsBmsSl-QLchOO\&q=85\&s=9a19b579cfda89d33c6d9a1314c2de62)

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

![Moogsoft: Create a Custom Integration in Moogsoft](https://mintcdn.com/germain-ux/ARpsBmsSl-QLchOO/images/main/moogsoft/image-20230717-210629.png?fit=max\&auto=format\&n=ARpsBmsSl-QLchOO\&q=85\&s=a8c9a4951358310bc252f8ffe5feb162)

If a custom inbound integration does not already exist:

**1. Sign in to Moogsoft APEX AIOps Incident Management**

**2. Go to Integrations > Inbound Integrations > Create Your Own Integration**

**3. Select Add New Integration**

**4. Enter a unique integration name and optional description**

**5. Select Events as the data type**

**6. Save the integration**

**7. Copy the generated endpoint and obtain an API key**

**8. Configure the required event-field mappings and severity mappings**

**9. 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](https://docs.moogsoft.com/moogsoft-cloud/en/create-your-own-integration--cyoi.html) and [Define a Custom Integration](https://docs.moogsoft.com/moogsoft-cloud/en/cyoi-define.html).

## Create the GermainUX HTTP Action

Go to:

**GermainUX Workspace > Automation > HTTP**

Select the **Add** icon to open the HTTP Action wizard.

![Moogsoft: Create the GermainUX HTTP Action](https://mintcdn.com/germain-ux/ARpsBmsSl-QLchOO/images/main/moogsoft/image-20230717-204839.png?fit=max\&auto=format\&n=ARpsBmsSl-QLchOO\&q=85\&s=713f141fee5de320bdce50c7c48c9262)

### 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

![Moogsoft: 2 Step 2: Configure the HTTP Request](https://mintcdn.com/germain-ux/ARpsBmsSl-QLchOO/images/main/moogsoft/image-20230717-205219.png?fit=max\&auto=format\&n=ARpsBmsSl-QLchOO\&q=85\&s=d1134a5935b4fd0c4e5a8c12e447c452)

| 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 |

![Moogsoft: 2 Step 2: Configure the HTTP Request, image 2](https://mintcdn.com/germain-ux/ARpsBmsSl-QLchOO/images/main/moogsoft/image-20230717-204745.png?fit=max\&auto=format\&n=ARpsBmsSl-QLchOO\&q=85\&s=feffa607584bce00b0feb7b0f688d7fb)

#### Example Request Body

```json theme={null}
{
  "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

```text theme={null}
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:

**1. Select the synthetic-scenario KPI**

**2. Configure or select its failure SLA**

**3. Add the Moogsoft HTTP Action as the SLA Action**

**4. 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

**1. Complete the wizard**

**2. Run the HTTP Action manually**

**3. Confirm that GermainUX receives a successful HTTP response**

**4. Open the Moogsoft custom integration**

**5. Confirm that the test payload appears in Map Your Data**

**6. Map the incoming fields to the appropriate Moogsoft event fields**

**7. Validate and enable the integration**

**8. 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](https://docs.germainux.com/main/support.md)**
>
> 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.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.