Micro Focus SiteScope – Tips and Tricks

Table of Contents

2. Micro Focus SiteScope – Tips and Tricks – Feb 2021

1. Instructions for restarting the Site Scope services on Windows

Users often go through difficulties when they try to reinstall Site Scope services on Windows. It can be fixed; users just need to follow specific rules. You can take help of the steps given below:

You need to execute the command given below:

SiteScopeService.exe -install <servicepath> <serviceparams> [servicename] [-force]

For the reinstallation of the SiteScope service, you can follow the steps given below:

  • You need to open the Command window as an administrator.
  • Then find the Site Scope root directory, under that, you will find Tools.
  • After that, you need to run the command, 

 SiteScopeService.exe -install <servicepath> <serviceparams> [servicename] [-force]

  • The previous step will let you create the registry key given below:

HKEY_LOCAL_MACHINE -> SYSTEM -> CurrentControlSet -> Services -> <SiteScope service> -> ServiceParam 

For Servicepath:

“<SiteScope root directory>\SiteScope”

You can take help from this example: “C\SiteScope”

ServiceParam:

"-Dcom.sun.management.jmxremote=true -Dcom.sun.management.jmxremote.port=28006 -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.ssl=false -server -Xmx512m -Xms512m -Xmn160m -Xrs -XX:+UseParNewGC -XX:+UseConcMarkSweepGC -XX:MaxPermSize=240m -XX:+HeapDumpOnOutOfMemoryError -showversion -Dcatalina.home="<SiteScope root directory>\Tomcat" -Djava.security.auth.login.config=file://///${catalina.home}/../conf/jaas.config -Dflipper.param.file=..\conf\flipperSiteScope.properties -Dtopaz.home=.. -Dnetworkaddress.cache.ttl=86400 -Dnetworkaddress.cache.negative.ttl=0 -Djavax.xml.parsers.DocumentBuilderFactory=com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderFactoryImpl -DSiteScope=true -cp "<SiteScope root directory>\Tomcat\bin\bootstrap.jar" org.apache.catalina.startup.Bootstrap start"

You need to carefully update the service path only in the ServiceParam string.

Another useful example:

"-Dcom.sun.management.jmxremote=true -Dcom.sun.management.jmxremote.port=28006 -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.ssl=false -server -Xmx512m -Xms512m -Xmn160m -Xrs -XX:+UseParNewGC -XX:+UseConcMarkSweepGC -XX:MaxPermSize=240m -XX:+HeapDumpOnOutOfMemoryError -showversion -Dcatalina.home="C:\SiteScope\Tomcat" -Djava.security.auth.login.config=file://///${catalina.home}/../conf/jaas.config -Dflipper.param.file=..\conf\flipperSiteScope.properties -Dtopaz.home=.. -Dnetworkaddress.cache.ttl=86400 -Dnetworkaddress.cache.negative.ttl=0 -Djavax.xml.parsers.DocumentBuilderFactory=com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderFactoryImpl -DSiteScope=true -cp "C:\SiteScope\Tomcat\bin\bootstrap.jar" org.apache.catalina.startup.Bootstrap start" 

The ServiceName will be:

servicename

This example will be useful for the versatile situations: “SiteScope.” 

Full command :

"SiteScopeService.exe -install "C:\SiteScope" "-Dcom.sun.management.jmxremote=true -Dcom.sun.management.jmxremote.port=28006 -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.ssl=false -server -Xmx512m -Xms512m -Xmn160m -Xrs -XX:+UseParNewGC -XX:+UseConcMarkSweepGC -XX:MaxPermSize=240m -XX:+HeapDumpOnOutOfMemoryError -showversion -Dcatalina.home="C:\SiteScope\Tomcat" -Djava.security.auth.login.config=file://///${catalina.home}/../conf/jaas.config -Dflipper.param.file=..\conf\flipperSiteScope.properties -Dtopaz.home=.. -Dnetworkaddress.cache.ttl=86400 -Dnetworkaddress.cache.negative.ttl=0 -Djavax.xml.parsers.DocumentBuilderFactory=com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderFactoryImpl -DSiteScope=true -cp "C:\SiteScope\Tomcat\bin\bootstrap.jar" org.apache.catalina.startup.Bootstrap start" SiteScope -force"

2. Details regarding the permissions that are needed to be assigned at the WMI namespace root\CIMV2

Users need to be well informed regarding all the details about WMI namespace root\CIMV2 so that they do not undergo any difficulty, this also includes the information about permissions. Users should know all the criterias regarding the permissions that are necessary to be assigned at the WMI namespace root\CIMV2.

You can configure the WMI service on the remote, server-

There are certain requirements for using Site Scope to collect the data and performance measurements on a remote machine, while using WMI:

  1. The WMI should be in good condition and running on the remote machine.
  2. The user that was logged in/entered on the WMI remote server needs to have all the necessary permissions to read statistics remotely from WMI namespace root\CIMV2.

It is necessary to add the monitoring user to the Performance Monitor Users group on the target server, and then you will have the DCOM remote launch and activate permissions

There are some preparations that you need to make:

  1. Site Scope needs to be installed on your Windows machine.
  2. Then you need to authenticate the WMI service on the said remote server:

There some  requirements for enabling SiteScope to collect performance measurements on a remote machine using WMI and they are given below:

  1. The WMI service needs to be running on the remote machine.
  2. The user previously entered on the WMI remote server should be permitted to read statistics remotely from WMI namespace root\CIMV2.
  3. The monitoring user needs to be added to the Performance Monitor Users group on the target server, and then you need to have DCOM remote launch and activation permissions.

Just for better understanding, you need to inspect the proper connection by checking the test utility. For this, Windows tool “wbemtest” is proven to be efficient, it tests the WMI connectivity between the two servers on the same subnet.

  1. Go to Start and then click on Run.
  2. Then write wbemtest and select on OK .
  3. Then you need to click on the Connect button.
  4. Then in the namespace given at the top, you need to type the IP address of the host that you are currently testing: \\x.x.x.x\namespace

In case the name space is there from the beginning then you do not need to worry, you can simply put the IP in front of it.

  1. Then you need to put in your Credentials for the host that you are trying to connect to.
  2. Then select the Connect button.

Once you are connected you will be able to view all the IWbem Services buttons that are available.

  1. Then you need to select the Query button and type the details given below:
select * from win32_useraccount

After this step, you need to verify the output carefully. 

3. Solving the “The Java Runtime Environment cannot be loaded” error

It often happens that users are unable to start Site Scope and an error dialogue box appears on the screen.

The error message being, “The Java Runtime Environment cannot be loaded”, or something of the same sort. This usually happens while initiating the Site Scope applet.You can solve this issue by following the steps given below, after every step you need to try to open Site Scope again, if it fails again then you should continue with rest of the steps:

After each step, try to reopen SiteScope. If SiteScope fails again, proceed to the next step.

  1. You need to close all of the browser’s windows.
  2. In case there are any background processes running then you need to stop them with the help of Windows Task Manager.
  3. Then you need to clear the local Java applet cache.

Click on Start, then find the Control Panel and select Java.

Then in the General Tab, you need to click on Settings and then click on OK.

  1. Then you need to clean the local Java applet cache, you need to do it by deleting the content of the folder given below:
C:\Documents and Settings\<user_name>\Application Data\Sun\Java\Deployment\cache.

4. Instructions to run Site Scope after the starting error from the 11.90 upgrade

It often happens that users are unable to initiate Site Scope on Linux Operating System, especially after upgrading from 11.41 to 11.90 version.

The update being: SiteScope 11.41 on Red Hat Linux has been updated to 11.90.

And after the upgrade Site Scope does not start in the basic way, that is <Sitecope>/start.

Users have observed that when they are executing the basic way, ./start, initially it works for a few moments but then the previous error pops up again. After this nothing is written in the error.log or in any other logfile.

Some basic fixes could be to start Site Scope through <SiteScope>/bin/go.sh.

If restarting the Operating System does not solve this issue then you need to use some other methods. As the main dissimilar fact between running start and go.sh is the service process start-service /com.mercury.sitescope.bootstrap.Service, due to this the error persists.

This error can be fixed when all the directives are removed that has jmxremote in it. You can do that by the steps given below:

Change in

go.sh
..
/opt/HP/SiteScope/java/bin/SiteScope -server -Xmx12288m -Xms12288m -Dcom.sun.management.jmxremote.port=28006 -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.ssl=false -Xss256k -XX:MaxPermSize=240m -XX:+UseParNewGC -XX:+UseConcMarkSweepGC -XX:-DoEscapeAnalysis -showversion -Dsun.net.inetaddr.ttl=0 -Dnetworkaddress.cache.ttl=86400 -Dnetworkaddress.cache.negative.ttl=0 -cp "../Tomcat/bin/bootstrap.jar:../Tomcat/bin/tomcat-extras-juli.jar" -Dcatalina.base="../Tomcat" -Dcatalina.home="../Tomcat" -Djava.security.auth.login.config=../conf/jaas.config -Dtopaz.home=.. -Djavax.xml.parsers.DocumentBuilderFactory=com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderFactoryImpl -Djavax.xml.parsers.SAXParserFactory=com.sun.org.apache.xerces.internal.jaxp.SAXParserFactoryImpl -Djava.util.Arrays.useLegacyMergeSort=true -Djava.security.manager -Djava.security.policy="../conf/security/sitescope.policy" org.apache.catalina.startup.Bootstrap start
..

to

..
/opt/HP/SiteScope/java/bin/SiteScope -server -Xmx12288m -Xms12288m -Xss256k -XX:MaxPermSize=240m -XX:+UseParNewGC -XX:+UseConcMarkSweepGC -XX:-DoEscapeAnalysis -showversion -Dsun.net.inetaddr.ttl=0 -Dnetworkaddress.cache.ttl=86400 -Dnetworkaddress.cache.negative.ttl=0 -cp "../Tomcat/bin/bootstrap.jar:../Tomcat/bin/tomcat-extras-juli.jar" -Dcatalina.base="../Tomcat" -Dcatalina.home="../Tomcat" -Djava.security.auth.login.config=../conf/jaas.config -Dtopaz.home=.. -Djavax.xml.parsers.DocumentBuilderFactory=com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderFactoryImpl -Djavax.xml.parsers.SAXParserFactory=com.sun.org.apache.xerces.internal.jaxp.SAXParserFactoryImpl -Djava.util.Arrays.useLegacyMergeSort=true -Djava.security.manager -Djava.security.policy="../conf/security/sitescope.policy" org.apache.catalina.startup.Bootstrap start
..

Then you need to remove: “-Dcom.sun.management.jmxremote.port=28006 -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.ssl=false”,

that’s all “-D” JVM directives with “jmxremote” in the name

  -Dcom.sun.management.jmxremote.port=28006 
  -Dcom.sun.management.jmxremote.authenticate=false 
  -Dcom.sun.management.jmxremote.ssl=false"

You need to do the same changes in the script start-service and start-monitor. Once this change is done the startup won’t check /opt/HP/SiteScope/java/lib/management/jmxremote.password anymore at all, and the Site Scope starts up properly.

5. Solving the “NoClassDefFound” error while starting SiteScope

Sometimes when users are starting the SiteScope applet it happens that they encounter a “NoClassDefFound” exception. When the applet fails to load with this error, users can follow these steps given below:

  1. You need to go to Java Configuration and then select the Keep temporary files on my computer option
  2. Then you need to go to the Control Panel and select on Java.
  3. Then under the General Tab, you need to select the Temporary Internet files and then Settings.

In case there are some issues regarding security, then you need to delete the temporary files on your own.

  • Then you need to close the SiteScope applet.
  • Then select Start, then find the Control Panel to select on Java.
  • Under the General Tab, you need to select the Temporary Internet files and then Settings and then click on Delete Files.

6. Fixing the SiteScope 11.92 / 2020.05 – Quick Reports Not Displaying error

It often happens that users encounter an error that says: SiteScope 11.92 / 2020.05 – Quick Reports Not Displaying. It is observed among the users that right after the upgrade to 11.92, the Quick reports do not run through any browser or SiteScope Client tool. Rest of the reports (daily email reports via email, management reports, etc) perform just as before.

Basically the user is not using the earlier default password for the keystore. These reports end up in failure due to the fact that the keys given below has a wrong password value for the keystore:

_httpSecureKeyPassword=ANYPASSWORD
_httpSecureKeystorePassword=ANYPASSWORD

This problem was tackled after updating those keys with the accurate password, in order to do that you can follow the steps given below:

  1. You need to stop SiteScope.
  2. Then make a backup of the configuration carefully.
  3. Then you need to change the previous wrong keys with the accurate ones that are given below:

You need to update them with the keystore password, that can be found at: <SiteScope>\groups\master.config:

_httpSecureKeyPassword=NEW_PASSWORD
_httpSecureKeystorePassword=NEW_PASSWORD
  1. After that you need to initiate SiteScope, and then you must test the reports.

7. Instructions to fix the error when the SiteScope – Automatic session timeout / users get logged out of SiteScope automatically / GUI / UI times out

Often users encounter an error that says, “SiteScope – Automatic session timeout / users get logged out of SiteScope automatically / GUI / UI times out / how to disable ro change the Session Timeout / how to prevent getting logged out of the SiteScope GUI after some minutes”. It is observed that initiating a particular version of Site Scope (after SiteScope 11.33) an idle session timeout has been already added that anyhow logs out uses after some period of inactivity. The set time for this is usually 20 minutes, but it is based on various environments so the logging out could also happen in less than 20 minutes. When the user is not using the SiteScope for not much time, it happens that abruptly the SiteScope GUI becomes grey and then another one gets a sliding bar. 

After inspecting and examining this issue, we can view at: <SiteScope>\logs\error.log

It would be logged into SiteScope through Internet Explorer at 13:17.

2020-09-28 13:12:54,821 [SiteScope Main] (SiteScopeSupport.java:729) INFO  - SiteScope 11.92.51  build 142 process started at Mon Sep 28 13:12:54 CEST 2020
2020-09-28 13:12:54,821 [SiteScope Main] (SiteScopeSupport.java:730) INFO  - SiteScope Start took 40 sec
2020-09-28 13:29:59,916 [HTTPRequestThread] (HTTPRequestThread.java:826) ERROR - Exception: java.lang.NullPointerException
java.lang.NullPointerException
      at com.mercury.sitescope.platform.httpserver.HTTPRequest.printHeader(HTTPRequest.java:999)
      at com.mercury.sitescope.platform.httpserver.HTTPRequest.printHeader(HTTPRequest.java:933)
      at com.mercury.sitescope.platform.httpserver.HTTPRequest.printHeader(HTTPRequest.java:927)
      at com.mercury.sitescope.platform.httpserver.HTTPRequest.printErrorMessage(HTTPRequest.java:110)
      at com.mercury.sitescope.platform.httpserver.HTTPRequestThread.run(HTTPRequestThread.java:771)
      at com.mercury.sitescope.infra.threads.ThreadPool$SingleThread.runTask(ThreadPool.java:462)
      at com.mercury.sitescope.infra.threads.ThreadPool$SingleThread.run(ThreadPool.java:488)
2020-09-28 13:30:01,104 [HTTPRequestThread] (HTTPRequestThread.java:826) ERROR - Exception: java.lang.NullPointerException
java.lang.NullPointerException
      at com.mercury.sitescope.platform.httpserver.HTTPRequest.printHeader(HTTPRequest.java:999)
      ..
2020-09-28 13:30:02,291 [HTTPRequestThread] (HTTPRequestThread.java:826) ERROR - Exception: java.lang.NullPointerException
java.lang.NullPointerException
..
The 13:17 (login) -> 13:29 (error) doesn't look like just 20 minutes but 12 minutes only
but
13:12 (SiteScope startup) -> 13:29 (error) looks a little closer to 20 minutes

In order to login once again the user needs to refresh the browser window. They just need to press CTRl along with Refresh in IE. These steps would take you to SiteScope Login Screen, often the screen is displayed without the fields asking for username and password, then you need to close the GUI and then re-open it. These log file entries mean something else entirely. They could also mean that the session timeout has started, and all of the messages are logged until the user logs in again. 

The timeout is actually a security feature, in order to handle the GUI timeout, you need to execute the steps given below:

  1. In <SiteScope>\groups\master.config you need to change _maxSessionTimeMinutes=20 (default) to _maxSessionTimeMinutes=-1.
  2. Then you need to restart SiteScope.

The users should note that this would also affect the integration with other products, like BSM/APM. The location where the user can lay their hands on Sitescope GUI through APM. You need to navigate to Admin and then select System Availability Management under that. In case it is not working with the GUI, SiteScope would force a logout, making it seem as if there is something faulty with the integration or SiteScope.

8. A list of all of the parameters that can be used in eMail alerts provided

At the time of setting up an alert in the SiteScope services using the Alert Action for sending an email. The user will be able to distinguish and specify templates for the email subject and also for the email body.

The templates that available can be found at

  Subject (that’s the email subject)

    <SiteScope>\templates.mail.subject

  Template (that’s the email body)

    <SiteScope>\templates.mail

This matter also depends upon the template, how many parameters are used, more or less. 

The default template

    <SiteScope>\templates.mail\Default
contains
***
This alert is from SiteScope at <newSiteScopeURL>
Monitor:  <groupID>:<name>
Tags:    <tag>
Group:    <group>
Status:   <state>
Sample #: <sample>
Time:     <time>
----------------------   Detail   ----------------------
<mainParameters>
<mainStateProperties>
***

In order to obtain a full list of all the parameters available the user can use the steps that are provided below:

You need to create a new template, for instance

  <sitescope_install_dir>\templates.mail\SG_All
which - additionally to keyword <all> - contains all keywords collected over time 
with the content (between **********)
**********
*** SG ***
-- status --
<state>
*** SG ***
*** SG2 ***
mainParameters - all of the parameters that appear on the Edit form 
<mainParameters> 
****
mainStateProperties - all of the result stats shown on the Reports 
<mainStateProperties>
****
secondaryParameters - all of the internal parameters 
<secondaryParameters>
****
secondaryStateProperties - all of the internal result stats 
<secondaryStateProperties>
****
all - all of the internal result stats 
<all>
*** SG2 ***
**********

Then the user will need to make a monitor (similar to a CPU monitor) with a threshold that would always trigger an ERROR (for example Error If utilization >= 0). Then a warning along with the email action and then you need to choose a new template (here SG_ALL) and then you need to wait for the alert to be implemented. Then you need to check the email message for the data that you need.

..
secondaryParameters - all of the internal parameters 
_class: CPUMonitor
_ownerID: 200981347
_id: 97
_nextID: 0
version: 11.92.51 12:00:00 2011-01-01 build 142
_parent: 200981347
_encoding: UTF-8
_errorTextLimit: 0
_goodTextLimit: 0
_topazId: 1006486
_internalId: 1951525443
_id: 97
_name: CPU sov02bac14
_maxrun: 600 sec
_ownerID: 200981347
****
..

Another example, in case you are into the SiteScope version, you can also get it through the variable/parameter “version”. If you need to use it in your template, you simply need to add (for example).

*****
This alert emal has been sent by SiteScope running version <_version>
The internal id of monitor <_name> is <_internalId>
*****
The next time the alert will be triggered, and it alert and send an email, it will contain
*****
This alert emal has been sent by SiteScope running version 11.92.51 12:00:00 2011-01-01 build 142
The internal id of monitor CPU sov02bac14 is 1951525443
*****

The users need to note that few parameters (like version) will be listed in the output as version: 11.92.51 12:00:00 2011-01-01 build 142 but it would also need to be referenced as “_version” in the template.

If the user is hesitant regarding which one to use, you can check that by adding the template given below for test:

***
version
<version>
***
_version
<_version>
***

Then the email will show:

***
version
<version>
***
_version
11.92.51 12:00:00 2011-01-01 build 142
***

So while utilising “<_version>” (without quotes) is actually the accurate name for the variable.

9. Details regarding SiteScope log file server_statistics.log / server_statistics_raw.log – and some values explained

This likely is only applicable to versions 11.33 up to 11.93, and could also be for earlier versions. The SiteScope log file server_statistics.log (under <SiteScope>\logs). It gives a few SiteScope server statistics, that are calculated and are logged every minute as a group of metrics. 

2020-11-17 15:26:57,528 [StatisticsLogger] INFO  - Used Memory=256MB   Available Memory=239MB   Total Memory=496MB   Max Memory=496MB
2020-11-17 15:26:57,540 [StatisticsLogger] INFO  - executionCount=2 averageTime=18,8ms driftAverageTime=0,0ms
2020-11-17 15:26:57,540 [StatisticsLogger] INFO  - PoolName=ProcessPool::perfex utilization=0,0% avgWaitInQueueTime=0 poolMaxSize=200 execTime=0
2020-11-17 15:26:57,540 [StatisticsLogger] INFO  - PoolName=ProcessPool::perfex_dispatcher utilization=0,0% avgWaitInQueueTime=0 poolMaxSize=200 execTime=0

At the time user is viewing the meaning of each individual metrics:

--> Used Memory=256MB   Available Memory=239MB   Total Memory=496MB   Max Memory=496MB

The similar code (/com/mercury/sitescope/platform/log/statistics/MemoryStatistics.java) will be used in the  SiteScope 11.33 and also in SiteScope 11.93, hence it will be applicable to every version between them:

It is recommended to utilize Java/JVM function calls for obtaining the metrics, and you can manually calculate two:

  usedmemory   = Runtime.getRuntime().totalMemory() - Runtime.getRuntime().freeMemory()
  availMemory  = Runtime.getRuntime().maxMemory() - usedMemory
  Total Memory = Runtime.getRuntime().totalMemory()
  Max Memory   = Runtime.getRuntime().maxMemory()

All of them are returned as expected and presented in MB, this is mainly performed by dividing the metric by BYTES_PER_MB (which is actually the SiteScope constant private static long BYTES_PER_MB = 1024 * 1024;)

An example for functions like the Runtime.gerRuntime() are provided below for reference purpose:

    What are Runtime.getRuntime().totalMemory() and freeMemory()?
--> executionCount=2 averageTime=18,8ms driftAverageTime=0,0ms

Once again the same code (/com/mercury/sitescope/platform/log/statistics/MonitorStatisticsLogger.java) is used in the SiteScope 11.33 and in SiteScope 11.93, so it will applicable to all the versions in between:

  executionCount   = the number of monitor executions during the measurement interval, which is 1 minute
  averageTime      = the average execution time for all monitors in MS executed during the measurement interval, which is 1 minute
  driftAverageTime = the average drift time for all monitors in MS executed during the measurement interval, which is 1 minute
                     while driftTime is the delta between the time a monitor should have been executed, and it was executed in the end

In order to overcome this problem the user can add metric on a per monitor basis by enabling DEBUG logging for RAW statics.

For using it, you need to enable DEBUG logging in

  <SiteScope>\conf\core\Tools\log4j\PlainJava\log4j.properties

change

  log4j.category.com.mercury.sitescope.platform.log.statistics.StatisticsLoggerRaw=WARN, statistics.logger.raw.appender

to

  log4j.category.com.mercury.sitescope.platform.log.statistics.StatisticsLoggerRaw=DEBUG, statistics.logger.raw.appender

The data will be logged to the SiteScope log file server_statistics_raw.log (<SiteScope>\logs),

SiteScope logs two lines per individual monitor and monitor execution, for example:

2020-11-23 11:28:19,799[DNS sov02bac19 via 15.119.182.2(200981347/57) ],DNSMonitor -545291160 546
2020-11-23 11:28:19,799[DNS sov02bac19 via 15.119.182.2(200981347/57) ],DNSMonitor,545,0,0 last= 1606127239255 cur=1606127299253 freq=60
in detail:
--> [DNS sov02bac19 via 15.119.182.2(200981347/57) ],DNSMonitor -545291160 546
  DNS sov02bac19 via 15.119.182.2(200981347/57) = monitor title (internal ids)
  DNSMonitor                 = monitor class
  -545291160                 = start time of the interval for which these statistics apply in nanoseconds - current time in nanoseconds
  546                        = current time in milliseconds - start time of the interval for which these statistics apply in milliseconds
--> [DNS sov02bac19 via 15.119.182.2(200981347/57) ],DNSMonitor,545,0,0 last= 1606127239255 cur=1606127299253 freq=60
  DNS sov02bac19 via 15.119.182.2(200981347/57) = monitor title (internal ids)
  DNSMonitor                 = monitor class
  545                        = execution time of this monitor in ms
  0                          = time the process had to wait for an entity out of the process pool
  0                          = monitor drift
  last       = 1606127239255 = last time the monitor was executed = EPOCH 1606127239.255 = 23/11/2020 11:27:19.255
  cur        = 1606127299253 = current time                       = EPOCH 1606127299.253 = 23/11/2020 11:28:19.253
  freq       = 60            =             

What we can observe is the following points:

The very monitor was executed the last time at 11/23/2020 11:27:19.255, 

Its execution took around 545 ms, 

The time the process had to wait for an entity out of the process pool was about 0 ms,

The drift time (delta between the time it should have been executed and it was executed in the end) was 0 ms, so NO drift

The last time the monitor was executed = 11/23/2020 11:27:19.255,

The current time (at the time this was logged) = 11/23/2020 11:28:19.253

The frequency (how often is the monitor configured to run) = 60 -> run all 60 seconds