You can change the display name of certain elements to help distinguish between each instance. Elements must have existing tags and attributes assigned in order to modify their display name in the UI.
${meta.originalName}
resolves to the name included with the original element payload before being replaced with the optional element name template. The Element Preview in the UI resolves this field to [original name]
as a placeholder because CloudWisdom only knows what the current name is, not what the incoming name might be.${tags.Name} (${attributes.privateIp})
returns something like MyServer (ip-10.101.3.99)
${tags.Name} (${attributes.availabilityZone})
returns something like ServerX (eu-west-1c)
${meta.fqn}
| e.g., 720523155433:ec2:us-east-1:i-20c9ae302d2e7b45e${meta.location}
| e.g., us-east-1${meta.type}
| e.g., EC2${meta.tenantId}
| e.g., 38907e4c-392a-9f9a-b682-7h938e43dt73${meta.id}
| e.g., 1f71ab78-80a9-3f9b-941f-07cbe8fe4703Not all element types have location metadata. Consider the type of element you are working with when customizing display names.
Adding the private IP address to your element names enables your team to immediately begin troubleshooting problematic instances.
<#if tags.Name??>${tags.Name}<#elseif tags.aws_autoscaling_groupName??>${tags.aws_autoscaling_groupName}<#else>${meta.originalName}</#if><#if attributes.privateIp??> (${attributes.privateIp})</#if>
This would produce an element name like acb03-aml-use1b (10.0.4.166)
for an EC2, SERVER, or WINSRV element.