21 Selenium startup error: on alertsite with chromebrowser
I am trying to build a selenium jar file on ubuntu wsl in an environment with chrome browser 85 using and I tried building it using java -jar command as mentioned in the document and it is working fine in my local environment. When I try to upload the JAR file built to alertsite via this code, it gives me error code 21 I did verify the main class is present in the jar file, and all the selenium libraries are installed as well. I presume its an issue due to the browser version mismatch on alertsite. Can someone let me know what the issue here is? which is the supported version on alertsite. Im not able to install older versions of chrome on my wsl as the official releases from google are removed. what can be done here? Thanks in advance PS: selenium version 3.141.59 and java version 11 i specify in my pom.xml during build.
Excel report using power bi
I work with a sizable real-time data set, and I utilise Power BI's dashboard to do certain analysis that I use every day to make choices, however the customer requires the monthly report summary in Excel. How do I link the Excel report form that I need to deliver the client with the Power Bi Course? The Excel report includes succinct charts and tables.
Blackout at system/account level instead of monitor level
Hi. New feature suggestion regarding blackouts... We have maintenance days scheduled throughout the year where we create a blackout using the bulk settings for all monitors. Even though we know the schedule for the entire year in advance, we cannot setup the blackouts in advance for the entire year because the blackouts are done at the monitor level. Meaning if I wanted to setup a blackout for an event three months from now, I can only select the monitors that exist at the time I'm entering the blackout. If any new monitors are created between the time the blackout was entered and when it actually takes place, they would not be included. Having a way to blackout at the account/system level that would include anything not yet created would be helpful.
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.Set Primary Location via API
I am trying to add a list of monitors using the API, I have all the necessary JSON field names, but I am getting an error that the "Primary location X is not in the listed locations home_location". I have set home_location to the id of our private node servers using both the text and number. Also The error "Primary location X, the X is not the correct number of the location when getting the location via API, I didn't know if the X is an error. Just a note I did try the location that was shown in the error, but still get the error. I can click in the GUI on the private node and set the primary location ok, just not via the API. I just need to know if this can be done via API, what is the correct JSON field name and what location number I should use or is the only choice that will I have to click through my list of sites after the monitors are created. Also I could be overlooking this, but what is the JSON field name used to set up alert recipient groups? If this can't be done via API is there a way to set it for a group of monitors all at once? Thanks for your helpConfigure 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.
