Improving SolarWinds SAM and Agent Monitor Usage , Problems getting "Location".

jjhj 16 days ago

Hi everyone,

I hope you’re doing well.

I’d like to start a discussion about an issue we’ve observed with the SolarWinds SAM module when using Agent Monitor on servers with multiple domains. According to SolarWinds support, the "Location" value is retrieved from the last DNS query made.

However, in a recent case, we noticed the following results from PowerShell:

NCOSOLB1 - "Location" value not obtained.
NCOSOLB2
NCOSOLB3
NCOSOLB4 - "Location" value not obtained.

This suggests that the "Location" value retrieval is not working as expected in some situations.

Topics for discussion:

Is this a common issue when using the SAM module with agents in multi-domain environments?
What configurations or best practices can ensure that values like "Location" are retrieved correctly?
If the issue persists, how can we manually set the "Location" value to ensure it applies properly?

Any previous experience or suggestions would be very helpful to improve the use of the SAM module and ensure accurate monitoring data.

Thank you all for joining this discussion. Looking forward to your input!

Top Replies

stevenstadel 16 days ago +1

Location was originally used to store the data from SNMP Location values, when the windows agent was introduced the field was repurposed for those specific machine types. The location value when it was…

stevenstadel 16 days ago

Location was originally used to store the data from SNMP Location values, when the windows agent was introduced the field was repurposed for those specific machine types. The location value when it was solely collecting from SNMP was only valuable if you had a rock solid build process and people following the same naming conventions. In my experience it was was not particularly useful once you had more then a handful of admins. I have never put much value in that data due to this and much prefer to use custom properties to determine things like location. You can control and auto populate custom properties with much more rigor.
Cancel
Vote Up +1 Vote Down

Sign in to reply

Cancel
bobmarley 14 days ago

As stevenstadel Location is derived from SNMP. We use a Custom Properties for items such as Location, Site Name, Street, City, etc. We have a mix of modes, some support the SNMP Location field, some (like ICMP Only nodes) will not respond back with that info. So without that info some of you nodes will always be blank.

It took some doing, but we aligned our subnetting with location 'source of truth' document showing the Physical location of all Subnets and trued that up with the location in the Custom Properties.

Hope that helps
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel