Retrieve AlertSite Usage Statistics via API
The AlertSite Usage Statistics (see https://uxm.alertsite.com/#/app/2/dashboard/as-account-settings-usage) include information such as: * Contract Term ( Start Date and End Date ) * Total Credits Used To Date * Total Credits Remaining * Daily Average over Last 7 Days and other useful information Can you make this information available via the API ? We would like to monitor our credit usage over time ThanksCustomize Alert Templates
Introducing Alert Template Customization AlertSite now supports the creation of custom alert templates. Multiple templates can be created for the same alert type, allowing you to target the right alert message to appropriate recipients. You can read more about Alert Template customization in UXM or in the 1.0 console.Screen Captures now included in email alert notifications!
We're excited to let you know that you can include screen captures as attachements in email alert notifications for browser monitors. To enable this functionality, select the checkbox next to the "Attach screen capture to E-mail alert" on the alert recipient configuration screen for any alert recipient. This configuration setting is only available in the AlertSite 1.0 console at this time. It will be added to AlertSite UXM soon. Any browser monitor configured for any level screen capture is supported by this new functionality.Active alerts on dashboard
on the dashboard, is there a way to highlight which monitors have active alerts? I don't care about errors, I want to see which monitors are in an active alert condition (maybe a sortable column). The errors screen is ok, but you have to read thru it. You can't quickly see the active alerts.
Configure Pause time duration prior to Local Retry
Local retry and Global Verify Tests are immediately scheduled following the initial failure that triggered the run in production testing. AlertSite today does not have a feature in place to pause the test for a duration of time before the next retry begins. The issue we have is when the AlertSite DejaClick script encounters a failure due to say a network blip, the retry is immediate. For some tests we would rather delay the Retry a few seconds. This would benefit the support team by not sending out alert notifications for false positives.
Custom Properties in Alert Templates
We've added custom properties to the available variables for editable alert templates. This allows you to easily add your metadata tags to alert payloads to make alert integrations even more powerful. You can add all properties with a single variable or include specific properties. Here's a quick look at how the new property variables are displayed in the alert template editor : You can read more about configuring custom properties HERE.Default Behavior for Monitors NOT in a Recipient Group 2022
Recipient Groups UXM (or Notifier Groups in AlertSite 1.0) allow you to define who will be notified when an alert for a specific device is triggered. The default behavior for any monitor that is not assigned to a group, is to notify all contacts on the recipient list according to the rules defined for each. It does not matter if a specific contact is in a group or not, the behavior is dictatedbased on the monitor disposition, not the recipients. Once a monitor is assigned to at least one recipient group, it will only notify recipients assigned to that group. Monitors can be associated with as many groups as you like, as can recipients. In the UXM console, you can configure a default group by navigating to the Alerts Tab > Recipient Groups screen. Next to the heading of any recipient group, Click the Flag icon next to a recipient group you would like to assign as the default group. In the AlertSite 1.0 console, you can tell which monitors are assigned to a notifier group under the Configuration tab. Any monitor that has the icon with the computer folders next to it is assigned to at least one group. In AlertSite 1.0, you can configure a default recipient group under the notifier groups configuration menu by navigating to Notifiers > Notifier Groups screen > Then clicking the Notifier group heading. Under the notifier group edit screen in 1.0, check the option for "Default Group will be used for all unassigned site" and click "Submit" button at the top right hand corner. Under the Account Preferences tab of the settings menu (Both UXM and 1.0 console) you can also disable notification for any new monitor you create by default. You can modify the settings for each monitor individually if needed. Another popular way to work around the default behavior is to create one 'Placeholder' group and assign all monitors to it, new and old. In this way, you can be sure that the wrong people are not notified if an error is triggered. You can then assign an invalid notification contact to the Placeholder group as well, or a contact who should be notified for all errors if one exists.
