I deleted metrics from SLM and isn't possible create it metrics again and see it

[Miller Echagarreta]

Hi everyone.
I am configuring sql_response probe, and all apparently okay. For a moment  I can saw metricas of my configuration but for some reason I no longer. So I configured again the sql_response and deleted the group metrics "sql_response" from SLM and "QOS" for that UIM to create metrics again but this metrics aren't create it again.

My configuration in sql_response is  ---->

Active metrics ------>

UIM not create it the metrics again ----->

Waht can I do ????

[Luc Christiaens]

After the delete:
- stop the sql_response probe
- restart data_engine
- restart sql_response probe

[Miller Echagarreta]

Hi @Luc Christiaens this steps not work. Do you have other procedure?​

[David Michel]

Just my opinion on what was initially done. It is best to not delete qos unless you are really sure that it needs to be done or it is just a test lab. 

There are two steps, creating the qos and creating the qos data. 

In this case apparently the qos was created correctly and then qos data stopped. 
One approach to take is troubleshoot the lack of new qos data. 

use drnimbus message sniffer filtered to the probe
deactivate the probe 
activate the probe 
monitor drnimbus for qos_definition messages, these are the ones used to create the qos

This will indicate the need to look further at the probe or the db side. 

Probably also good to clear niscache at the robot.

------------------------------
Support Engineer
Broadcom
------------------------------

[Miller Echagarreta]

Hi @David Michel I clearly made a mistake​, now I need to solve it.
I make this, but not resolv the problem.
1) Deactivate sql_response
2) I applied with probe utility
     _nis_cache_clean
     _reset_device_id_and_restart
3) check with doc nimbus that QOS_DEFINITION has been created
I think that may be the data_engine doesn't create the QOS sql_response again?
Is possible repair this? may be to create manually the QOS in db? I don't know if this is the best practice.

[David Michel]

My intention was to provide guidance for others to consider the options prior to slm qos delete, and not to point out a potential mistake made. 

qos_definition messages should be sent every time a probe is activate and which ones sent will depend upon which qos has been enabled. 

If the probe is no longer sending the qos_definition messages consider:
ensuring robot is either robot_update-7.97HF6.zip or 9.2 if UIM 9.0.2 or 9.2.0 is used
delete the probe from the console
delete the probe folder 
clear the niscache folder at the robot
restart the robot
deactivate discovery_server
deactivate data_engine
activate data_engine
activate discovery_server
deploy the latest revision of the probe
reconfigure 
check for qos_definition messages

others with more experience may have a different order for some of the above &/or different advice.

------------------------------
Support Engineer
Broadcom
------------------------------

[Miller Echagarreta]

Thanks @David Michel for all your support.

The robot ​if it's sending QOS_DEFINATION, but the QOS is not being created in the "SLM" I don't know what else to do

OQS_DEFINITION sending from robot ------>

On SLM not create the QOS

[Jason Allen]

I recommend checking the data_engine log on level 3 or higher, and watch for errors regarding this QOS.     I suspect data_engine is having some trouble inserting it.

[David Michel]

for my part, 
deactivate data_engine
activate data_engine
rather than just relying on the auto restart when saving the log level change

------------------------------
Support Engineer
Broadcom
------------------------------

[Miller Echagarreta]

Hi All.

I fixed the issue. Only create other profile with other query in sql_response and the QOS has been created again

thanks to all.