Moogsoft

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

⚙️ Create a Custom Integration in Moogsoft

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

Select Next.

2️⃣ Step 2: Configure the HTTP Request

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

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

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

🛡️ Security and Operational Considerations