Interesting idea. Maybe use nexec or logmon to trigger a powershell command.. i will test that. Thanks
Original Message:
Sent: Oct 24, 2024 03:54 AM
From: Luc Christiaens
Subject: Using robot variable in sqlserver connction/profile strings
Hi David,
Perhaps you can try the package "post install command" to replace the "$robot" by %computername% (if windows) by one of the available replace utilities, like sed, fnr, ..?
Original Message:
Sent: Oct 24, 2024 03:31 AM
From: David Givens
Subject: Using robot variable in sqlserver connction/profile strings
Hi Rajesh,
Thanks for the input
I didnt, but the reason I didnt is because, if memory serves me correctly, the profile name or connection name is used in qos source/target generation so they would come back as 127.0.0.1 in QoS metrics.
Original Message:
Sent: Oct 24, 2024 03:26 AM
From: Rajesh Banuka
Subject: Using robot variable in sqlserver connction/profile strings
Hi David,
Did you try with localhost or 127.0.0.1 as conn_string parameter. Hopefully it should connect to the local DB instance and metric or alarms gets correlated to the Robot.
Rgds,
Rajesh b
Original Message:
Sent: Oct 23, 2024 04:16 AM
From: David Givens
Subject: Using robot variable in sqlserver connction/profile strings
Hi all,
I am wondering if its possible to use variables in the sqlserver probe ?
I have a large number of sql server servers to monitor and they all use the default instance, which matches the robot name.
I have created an package to use $robot but this doesnt seem to parse. I am assuming it is not possible, but thought I would confirm/check.
For example
<$robot> overwrite
user = user
password = pass
auto_domain = yes
description = $robot
conn_string = $robot
retry = 4
retry_delay = 2 min
winauth = 1
encryption = no
enable_CrossDomain_conn = no
timeout = 1 min
monitor_AlwaysOn = no
is_AlwaysOn =
tls_enable = no
</$robot>
Thanks
