Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Introduction

...

Now, let's define when the override will perform validationbe active. You may choose to run have the override active on a specific day and time. If no day is specified, it will run days of the week and at any time. By default, all weekdays are selected, so it will be active daily at the indicated time. Alternatively, you can assign a pre-an existing schedule from the dropdown menu. This will override the scheduling parameters mentioned above, and the override will be active when the schedule is On.

[Aggregation]

The next section is where you define the aggregation values. Since we're creating from a template, these are already pre-filled. However, should you wish to modify them, each field can be adjusted according to your requirements.

...

Now, we're ready to define the threshold values. These fields are also pre-filled already, but they can also be adjusted.

  • Warning

    • Warning Value

    indicates
    • defines the threshold value that,

    if met, raises a warning threshold violation
    • when met based on the specified operator logic, sets monitor severity to Warning or the severity level configured in the Warning Severity field. that determines whether the limit has been reached. If this field is left blank, it means a warning is not used. If this field is left blank or set to zero, it signifies that no data is available.

    • Warning Operator

    indicates
    • is the logical comparison operator used

    for validation
    • to check the Value matching Warning threshold.

    • Warning Severity denotes the monitor severity

    status
    • that will be

    triggered
    • set when the

    validation meets the Warning Value.
    • value matches the warning threshold.

  • Alarm

    • Alarm Value

    refers to
    • defines the

    specific
    • threshold value that, when

    reached or exceeded, triggers an alarm
    • met based on the specified operator logic, sets monitor severity to Alarm or the severity level configured in the Alarm Severity field. If this field is left blank, it means an alarm is not used.

    • Alarm Operator

    refers to
    • is the logical comparison operator used

    to evaluate the condition
    • for

    triggering the alarm
    • checking the Value matching Alarm threshold.

    • Alarm Severity

    indicates the level of criticality associated with the alarm. In IT-Conductor, we have these available for selection.
    • denotes the monitor severity that will be set when the value matches alarm threshold.

  • Finally, Reset After defines the duration or conditions under which an alarm will automatically reset or be cleared after being triggered.

...

  • Alert On refers to the status that will trigger the alert and notify the users. This is usually set to “Warning”.

  • Alert Message refers to the message that the users will see. This message is customizable by the user. (Pause for 7 seconds before proceeding to the next fields)

  • // Note on Screen // You may refer to the Threshold Overrides Variables in the IT-Conductor Knowledge Base for more details.

  • Repeat After refers to the setting that determines how long the system should wait before sending a subsequent alert after the initial notification has been triggered. For example, if an alert is triggered and the Repeat After duration is set to <120> minutes, the system will send another alert if the condition is still active after that time has passed. You can also define the time period interval for which alerts will be raisedgenerated. You can also define the duration for which this condition remains active before subsequent alerts are sent.

  • Alert Priority refers to the classification that determines the urgency and importance of an alert within a monitoring system. In IT-Conductor, we have these available for selection.

  • In the Notification Template field, you can select a predefined template to ensure that alert notifications adhere to a standard format.

  • Resolve Alerts allows users to mark alerts as resolved when the alert is no longer active or when the metric falls below the configured threshold value.

  • If you want to receive an alert and notifications when the system returns to its normal status, check the Alert On Normal checkbox and optionally specify the alert text.

  • The Escalate feature allows you to set rules for how alert escalation is handled:

    • if they remain unresolved for a certain period.

    • If the number of repeated alerts (based on the rule criteria) exceeds the specified value

    • An escalation Alert is created depending on the rules, that alert can be picked up by a subscription that targets the management

...

Next, you’ll need to define which Recovery action the system will take. This might include restarting a job or executing a specific recovery script. IT-Conductor provides predefined recovery activities based on common scenarios, which you can easily select from the list. Any custom recovery Custom recoveries can be implemented in collaboration with the IT-Conductor Support Team.

[Saving & Verification]

Once all fields are filled out properly, click Save to complete the configuration.

...

For the rest of the video, follow along with the configuration steps being shown.

In this example, we’ll show how to create an override that will be triggered once 800 or more users have logged in to the system.

In Alert Message, with the help of the Variables button, we’ll write the message that will be sent once the 800 users threshold has been breached.

If you want to review what each field does, feel free to revisit the previous part of this demo or visit the IT-Conductor Knowledge Base at your convenience.

...