Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials

Adding Custom property automatically when node added to group

In SolarWinds I have create a custom property for address, latitude and longitude, How do I add the custom property for latitude, longitude and address to a group
In solarwinds so that it automatically populates those values when you add a node to the group.

Find more posts tagged with

Accepted answers

All comments

cnorborg

Here is a question, why not add the custom property to the Group itself? Seems a bit easier?

In the "Add Custom Property" in the left hand column just choose to add it to group instead of node.

PCMillard1

Would that work for location type information.

Trying to make sure the address and lat and long is correct for each node if adding the specific custom property eg 10 Anywhere street, Lat 10deg N log 8 deg w etc, to a group would work then yes it would be easier.

vinay.by

Can you please help me understand the use case, why do you want to carry these values onto a group? Are you trying to add groups onto a map or something?

Automatic/Manual population of these custom properties on node seems right. What is the intent of moving these values to a group ?

PCMillard1

That's exactly right, I am trying to populate these onto a map and have the address as a variable that can be pulled into fields in alerts.

romeo-donca

Ok, so for my understanding, when you add a new node in a group, the group need to have node's latitude and longitude values
Can be done but reactive with a scheduled job
First - you should keep ion mind 2 cases. One of these cases is when a group is not created based on location criteria. In this case your request is not applicable
So you need to make difference for your groups - the easieast way is to name these groups ( based on location criteria ) to add a prefix in the name like - location/branch/site… - ex site_group1
If you don't like that, create a new custom property for the group to differentiate the groups ( based on location or business/operational purpose )

Next you will need a script, scheduled job to parse all graoups , based on how you made the difference ( prefix or group custom property ) and if lat and long for a specific group ( location based ) are empty, willcopy the values from the member node to group's custom properties

Let me know if make sense for you

bourlis

I actually do something like this right now. Here's what I have setup

I setup a foundation trigger item. This could be a site naming standard, IP address range, a single custom property, or multiple custom properties like floor, comm-room/data center row.
This is an example of an alert that I have setup.
- Trigger Condition
  - I want to alert on Node
  - Only the following <ands>
    - Node IP address range contains "10.100.100"
    - Node Custom Properties Floor is equal to "10th fl"
    - Node Custom Properties Site 'Sales'
  - The actual trigger cognition <ands>
    - Node Custom Properties Location is empty
    - Node Custom Properties Street address is empty
    - Node Custom Properties Latitude is empty.
    - Node Custom Properties Longitude is empty.
- Reset Condition
- Trigger Condition
  - I want to alert on Node
  - Only the following <ands>
    - Node IP address range contains "10.100.100"
    - Node Custom Properties Floor is equal to "10th fl"
    - Node Custom Properties Site 'Sales'
  - The actual trigger cognition <ands>
    - Node Custom Properties Location is not empty
    - Node Custom Properties Street address is not empty
    - Node Custom Properties Latitude is not empty.
    - Node Custom Properties Longitude is not empty.
- Tigger Actions
- <You'll need a separate Change Custom Property action for each custom property you'll want to set>.

I like to send an email to my team, the team who's responsible for this node and the asset management team when this complete. Here's what my emails look like

Hello ${_Primary_Contact},
Please be aware the SolarWinds just change the custom properties for ${NodeName}.
The changes were for made for SolarWinds to PagerDuty alerting enhancements. The following custom properties were changed.
_Disposition: ${N=SwisEntity;M=CustomProperties._Disposition}
PDUrgendcy: ${N=SwisEntity;M=CustomProperties.PDUrgency}
Notification Profile: ${N=SwisEntity;M=CustomProperties.Notification_Profile}
Thank you,

I have these alerts setup with a different naming standard so that they stand out. For example if this was my alert it would look like this:

(SW System) Sales on 10th Ave and Main dynamic CP update.

with a description that says:

This alert will dynamically update the street address, longitude and latitude based on the building name, IP address and floor.

You don't need reset actions or anything more than what I've shown. It's really simply and I have a bunch of them. What's really nice is you can change these in a heartbeat. Just by adding or removing trigger conditions.