Edit an Activity's Properties

You can change an activity's properties to change its name in the dashboards, or change the group of devices where this activity is deployed, or change its thresholds to alter when it generates incident alerts or SLA violations in the Monitor SLA dashboard.

For example, when you first upload a custom activity, you can restrict its deployment to the test group, then after testing, you can edit the activity's properties to change its deployment to cover all users.

Edit an activity's properties

Before you begin

Add an application as managed to enhance its monitoring to include its PRC, launch times, and define any custom activities to measure the response times of specific user activities.

You must first create a custom activity (learn more) then upload its core definition (signature file) to Aternity (learn more).

Procedure

  1. Step 1 Open a browser and sign in to Aternity.
  2. Step 2 To edit the properties of an existing activity (not its core definition), select the row's context menu on the right > Edit.
    Tip

    To update the core definition of an activity, update its signature file by selecting the row's context menu on the right > Upload signature. This step only refers to changing the properties of an activity, not its core definition.

    Edit the properties of an activity
    Field Description
    Start Activity Monitoring

    Select to enable or disable this activity in the deployed group specified in Deploy to.

    When you disable an activity, Aternity tells the devices in that group to stop reporting performance for that activity.

    Activity Name

    Enter the name of the activity as it should appear throughout the dashboards.

    Tip

    If you change an existing name, the dashboards display the new name as a separate entry, starting its own new history. For a week since the change, you can continue to view its previous data under the old name.

    Deploy to

    Choose the group of devices which should report performance data for this entry:

    • Test Group indicates that Aternity only monitors this entry for users or devices in the test group.

    • All Users indicates that Aternity monitors this entry for all reporting devices.

    • Custom indicates that Aternity monitors this entry for users or devices in a custom group that you created.

    • Multiple indicates that Aternity monitors this application for several different groups, which are assigned to different activities of the application.

    Enable Incident Detection

    Select to enable or disable reporting incidents from this activity's performance in the deployment group. By default, Aternity enables an activity's incident detection.

    Incident is set when

    Enter the settings for Aternity to trigger an incident for this activity when BOTH:

    • # Users There are at least this number of unique Windows usernames in this deployment group which suffer poor performance (activity status is major ).

    • % Users There is at least this percentage of unique Windows usernames in this deployment group which suffer poor performance (activity status is major ).

    Tip

    If these fields display N/A, check your incident detection advanced settings in the Monitors Settings tree.

    A Power User of Aternity can edit the email notification template for incidents by selecting the Gear Icon > Settings > Advanced Settings > monitors > defaults > IncidentAlertSettings > message, edit the message, and then select Publish.

    Enable Incident Email

    Select to enable the functionality of automatically sending a mail when Aternity detects an incident.

    Without emails, you can see incidents in the Incident List dashboard.

    Email to

    Enter the email addresses to send an alert message whenever Aternity automatically opens an incident on this activity. To enter more than one address, separate them with a semi-colon (;) only, no spaces. You can set the default email for incidents by selecting the Gear Icon > Settings > Advanced Settings > monitors > defaults > IncidentAlertSettings > toRecipients.

    Note

    If you are a multi-tenant service provider, you can set up an email address for each account.

    Enable SLA Thresholds (Internal / External)

    Enter the SLA thresholds of this activity:

    The Internal threshold is the response time (in seconds) of an activity which would be your early warning, showing you are at risk of exceeding your official service level agreement (SLA) with your customers. Any response longer than this threshold is colored yellow in the SLA dashboard, as it warns you risk breaking the SLA commitment for this activity.

    The External threshold represents the maximum response time (in seconds) of an activity as defined in your official service level agreement (SLA) with your customers. Any response longer than this threshold is colored red in the SLA dashboard, since it breaks the official SLA commitment for this activity.

  3. Step 3 To edit several activities at once, select their check boxes, then select Bulk Actions.
    Change several activities at once
    Field Description
    Start

    Select to enable all the selected activities so devices start monitoring their performance in their deployed groups.

    Stop

    Select to disable all the selected activities so devices stop monitoring their performance in their deployed groups.

    When you disable an activity, Aternity tells the devices in that group to stop reporting performance for that activity.

    Rollout

    Select to assign the same deployment group to all the selected activities. If you select activities with different deployment groups, it displays them initially as Multiple.

    Incident Detection Settings

    Enter to enable or disable the ability of all these activities to raise an incident, and enter the same incident settings for all of them.

    SLA Thresholds

    Select to enter the same SLA thresholds of all the selected activities.

    Delete

    Select to remove all selected activities from this application.