the next step would be to open up DR nimbus and point it to the local hub for the robot where the probe is and set the probe to sqlserver and the robot.
Then deactivate and activate the sqlserver probe.
You should see qos_definitions and then qos coming.
If you do not then you have a problem with the robot /spooler or the probe. May try reinstalling or upgrading versions.
If you do see the qos info then move to the next hub in the chain on the way to the primary and repeat.
You will need to find where the messages stop.
If you get to the primary hub and see the messages coming in then check the data_engine loglevel 3 or higher logs for dropped messages.
------------------------------
Gene Howard
Principal Support Engineer
Broadcom
------------------------------
Original Message:
Sent: 08-10-2020 07:18 AM
From: amar kondraju
Subject: sql server probe qos is not showing
Hi all,
I have checked the below query as well but we are unable to see the qos for the required robot in database. We have enabled some of the chekpoints/qos in sqlserver probe but its not reflecting in database. Need some quick help.
select * from s_qos_data where qos like 'qos_sqlserver%'
Regards
Amar
Original Message:
Sent: 08-04-2020 10:22 AM
From: GREGG STILLWELL
Subject: sql server probe qos is not showing
Try this to get data from sqlserver. Then compare source. sometime sqlserver may be configure to give different source then robot. You can also check qos_sqlserver in SLM and Performance Reports QoS tab.
select * from s_qos_data where qos like 'qos_sqlserver%'
Original Message:
Sent: 08-04-2020 08:59 AM
From: amar kondraju
Subject: sql server probe qos is not showing
Hi all,
sql server probe and qos is not showing when I am trying to run the below query in SLM. Why is this? I am able to see sqlserver probe running fine in the robot where I have deployed in UIM.
select * from s_qos_data where source like '%hostname%' ---> hostname i am mentioning generally but in specific I am mentioning there while running.
Regards
Amar