Automatic SLA Alerts

SLA Configuration

For you to start receiving the SLA alerts on the IPA probe measurements, you will need to:

  • define the SLA levels;
  • define configurations for the SLA levels;
  • define for each IPA Transaction Flow what is the SLA configuration you want!

SLA Levels

You start configuring what SLA levels you want, each SLA level represents a percentage amount of transaction executions.

So if you have a transaction with 8 data points (probes), and execute in your application the process that passes through these probes 100 times, you have 1 transaction being executed 100 times, each execution taking a specific number of milliseconds to go through the 8 probes.
This percentage you define here is the threshold against which those 100 executions will be measured (see more info on this below).

You can add as many levels as you wish:

You can also edit SLA Levels clicking on each level name:

SLA Configurations

Having defined your SLA Levels, you will then create one (or more) SLA Configurations:

In each SLA Configuration you can define:

SLA Notification Config

  • to whom the notification will be sent
  • the frequency of analysis (Digest Frequency)

If the Endpoint URL is filled up, a POST call will be made to that URL with the following body:
{
LevelPercentage: int,
Percentage: int,
PartialTransactionsCount: int,
TotalTransactionsCount: int,
FlowName: string,
LevelName: string,
ConfigName: string,
Milliseconds: string,
NotificationType: string ("InBand", "OutOfBand")
}

If the fields Http Auth Username and Http Auth Password are used, IPA will use those values for authentication.

Performance Level Config

  • for each SLA % Level, what is the threshold amount of time in milliseconds

So here you are matching the SLA % Level defined previously with a Transaction Time threshold.

This Performance Level Config, for the most commonly used "in-band" type, means that:
a) For an IPA Transaction Flow with for example 100 instances/executions;
b) IPA will be evaluating the transaction time of each execution (from the first data point to the last);
c) IPA identifies the percentage of all transaction executions that are below the specified Transaction Time for each Transaction Level;
d) If the percentage identified in c) is below (in-band) of the SLA Level Percentage, IPA will send a notification.

SLA Flows

After defining the SLA Levels and the SLA Configurations, you will need to say to which Transaction Flows do you want to apply each SLA Configuration.

IPA will automatically show you all Transaction Flows it has already detected through the IPA Probes you previously setup and the different executions your users are doing in your application.


What’s Next

See our Metrics page to understand what IPA dashboard does for you, and how to drill down to the level of the probes data-points

Did this page help you?