Create an Alert

Alerts Overview

Alerts are one of several notification and automation capabilities available in GermainUX. They notify selected recipients when an SLA is breached or another configured condition requires attention.

See Notification Types for other available notification mechanisms.

⚙️ Create or Edit an Alert

Go to:

Germain Workspace -> Left Menu → Settings → Automation -> Alerts

From the Alerts screen, you can create, update, enable, disable, or review alert actions.

Most configuration fields include tooltips explaining their purpose and expected values.

📡 Local or Remote Execution

An alert can be executed:

Use remote execution when the alert must access resources, networks, scripts, or services available only from a particular monitored environment.

🔔 Trigger an Alert from an SLA

An alert can be assigned to an SLA from either the KPI or SLA configuration.

Go to:

• Germain Workspace -> Left Menu → Settings → Analytics -> KPIs

• Germain Workspace -> Left Menu → Settings → Analytics -> SLAs

Then:

1. Select or create the KPI.
   

   

2. Select or create the SLA.
   

   

3. Configure the SLA condition, evaluation period, and measure.

4. Select an alert template.

5. Select the Alert Action.

6. Save the configuration.

When the SLA is breached and its activation requirements are satisfied, GermainUX executes the Alert Action.

⏳ SLA Evaluation Example

Assume an SLA is configured with:

• Period Count: 5

• Granularity: Minutes

• KPI Measure: Average CPU Usage

GermainUX evaluates the average CPU usage recorded during the previous five minutes.

Other examples include:

• A period count of 2 with a granularity of Days evaluates the previous two days.

• A period count of 30 with a granularity of Minutes evaluates the previous 30 minutes.

📃 Alert Templates

Alert templates define the message delivered to recipients. Templates can contain KPI, SLA, application, system, user, error, and other contextual information.

The preview capability lets you review the rendered message while editing the template.

See Configure Alert and Report Templates.

🔗 Execute an Action from an Alert

An alert template can include a link that lets an authorized recipient execute a GermainUX action.

🔗 Action Link Without Additional References

<a href="${links.executeAction('Test Action')}"->
    Execute action: Test Action
</a->

🔗 Action Link with Additional References

<a href="${
    links.executeActionWithReferences('Test Action')
        .addConfigReference(
            'Server',
            'germain.apm.monitoringConfig.dataSources',
            'DS Name'
        )
        .addConfigReference(
            'Credentials',
            'germain.apm.monitoringConfig.credentials',
            'Example Credentials'
        )
        .addValueReference('Var1', 'Variable 1')
        .addValueReference('Var2', 'Variable 2')
        .build()
}"->
    Execute action: Test Action
</a->

The referenced values become available to the executed action as:

References already defined on the ActionConfig object remain available automatically. Template links can add dynamic references required for a specific execution.

📋 Alert Configuration Reference

See Quiet Time for additional configuration details.

✂️ Reduce Alert Volume

GermainUX provides two primary mechanisms for limiting repetitive alerts.

🔇 Quiet Time

Quiet Time is configured on the Alert Action.

After the alert fires, GermainUX suppresses additional executions of that alert during the configured quiet-time period.

Use Quiet Time when repeated SLA violations would otherwise generate multiple notifications for the same ongoing issue.

🔢 Activation Count

Activation Count is configured on the SLA.

The SLA Action is triggered only after the configured number of violations has occurred.

For example, an Activation Count of 3 requires three qualifying violations before the alert is sent.

Go to:

Germain Workspace → Left Menu → Settings --> Analytics --> SLAs

Quiet Time limits repeated notifications after an alert fires, while Activation Count prevents an alert from firing until the required number of violations has been reached.