Error while creating Synthetic monitor in Dynatrace

We have seen that we get below listed error while creating Synthetic monitors in a particular Management Zone in Dynatrace.

Your monitor can't be created because the selected management zone doesn't allow synthetic monitors. Either select a different management zone (see filter icon in the menu bar above) or contact your Dynatrace administrator." Can someone let me know the cause for this issue and how to resolve it?

This generally happens if there is no proper RULE applied to the MZ which included Synthetic monitors.

This might also happen if you are not using proper Monitor name or tagging or you do not have "Change Monitor Settings" checked for particular MZ.

Issue while moving tiles on Dynatrace Dashborad

 This is a known issue and there is no fix yet from the provider.

This only solution to this is (a temporary workaround) is to set zoom back to 100% when it refuses to work. Try zoom in and zoom out whichever works in your case.

Someone is definitely working on this from the vendor's side but there is no ETA.

What Is Sonic Bus?

In earlier versions of BAC like 7.5 it was called BUS. Back then, it was Mercury's creation and BUS was based on C. After HP's acquisition, they decided to use an external, third-party product called Sonic BUS - based on java.

What you need to know about bus:

* Sonic bus is the bridge between your BSM Gateway and Data Processing servers

* Data from your Data Collectors (BPM, RUM, SiteScope, Diagnostics, OMW/U etc.) comes to your Gateway server and goes to the Sonic BUS. From there, different components catch the data and use it for their own purpose:

    - db_loader inserts this raw data in your Profile database, so it can be used for reports for example. Based on this data, you get aggregated data. No data from db_loader, no reports.

    - the MARBLE (former online_engine) components of BSM use the Sonic BUS to catch your data and color your views (Dashboard/Service Health).

* Sonic BUS mainly consists of two parts - Message Broker and Domain Manager. MB is located on both Gateway and Data Processing servers, whereas the DM resides only on the Data Processing one. Your data is being transferred between the MB of the two servers.

* Message Broker and Domain Manager work by default on respectively ports 2507 and 2506. Sonic BUS also uses a wide range of dynamic ports.

* Sonic BUS has its own local database (on the BSM file system) - the information that goes to it is not stored in the Database server!

* If you access your BSM servers, go to Start > Programs > Progress, you will find the Sonic BUS management console (press ok to login). From here, you can manage and view the data that is in the Sonic BUS queues.


The Sonic BUS application is a very sensitive one. Always proceed with caution when working with it and avoid any modification, unless you are 100% aware of what you are doing or you are instructed by Support.

How HP Sitescope works!

How HP SiteScope works

HP SiteScope provides a centralized, scalable architecture. HP SiteScope is implemented as a Java server application and runs on a single, central system as a daemon process. The HP SiteScope Java server supports three key functions: data collection, alerting, and reporting. All user interaction is accomplished through a Web-based user interface that enables configuration, installation, administration, real-time status, and reporting from one seamlessly integrated console.

Sitescope Architecture

Sitescope consists of following components:

·         Browser based interface – Manages end user status information requests, configuration changes requests and access control.

·         Scheduler – Coordinates the running of monitors, alerts creation and report generation.

·         Monitors – Collects performance and availability information about the system being monitored.

·         Alerts – Notifications of exceptions, failures and status changes events in the system being monitored.

·         Reports – A historic representation of monitored data for trending and analysis purpose.

How to capture the URL that is formed because of redirection?

Example:
When visiting http://www.mercury.com, user will be redirected to a different location. How to capture the redirected URL.


Solution:
Use web_reg_save_param()

When that the server redirects a HTTP request to another URL, it normally does that by sending a HTTP 302 Moved header. To verify
1. Run the script in extended log with "data retuned by server' turned on
2. Check the execution log for "302 moved'

You can also see that along with this header, the server also sends the following header information:
   "Location: ."

The URL specified in the "Location' header will be the URL that the original HTTP request be redirected to. To capture this URL, you have to capture the string between "Location:" and "\r\n" (end of line).

Example:

    Action()
    {

       //use the correlation statement to capture the redirection
       web_reg_save_param ("Redirection", "LB=Location: ","RB=\r\n" ,LAST );

       //Visit Mercury homepage
       web_url("Mercury","URL=http://www.mercury.com/", LAST);

       //Print the redirected URL
       lr_message("redirected address = %s", lr_eval_string("{Redirection}"));

       return 0;
    }

How to Set Proxy Values for all the Ajax TruClient Scripts?

LoadRunner launches Firefox in a temporary profile every time a script is opened for development.

To make the proxy settings available across all these profiles please use the global profile settings do this:

• Open VuGen.
• Open an Ajax TruClient script.
• Go to Tools > Ajax TruClient Browser Options…
• In the dialog that opens (“Ajax TruClient Browser Configuration”), select the Proxy tab and
define the appropriate Proxy settings.
• In the script, open the Run-Time Settings dialog and then select the General > Other Settings
node.
• In the Proxy selection node select the “Use global proxy settings” option. This will make sure
that every time the script is opened for development the proxy settings are refreshed from
the Ajax TruClient Browser Options.

The Run-Time Settings also enable defining specific proxy settings for each script.

How Can I Use JavaScript to Locate Objects in Ajax True client script?

Using the JavaScript identification method you can write JavaScript code that references the returned
document and can use CSS selectors and other standard functions.

For example, the page returned by the server contains multiple links with the same “title” attribute
(search results) and we want the script to randomly click on one of the available links.
Object identification for this case, using the JavaScript identification method, may look something like this:

var my_results = document.querySelectorAll('a[title="SearchResult"]');
my_results[Math.floor(Math.random() * my_results.length)];