Entity types
The Topology Service allows you to group resources of the same type that uses the entityTypes
property, and identify them in the UI by their icon.
Usually a resource has only a single entity type, but, as the property is a Set, it is possible for a resource to have more than one entity type. Pre-defined associations of icons to specific entityTypes are listed in the following sections. You can create additional entity types as required.
- An entityType is defined by defining a resource with that type in the entityTypes list field.
- You can associate icons with named types in the Topology Viewer.
- You can add custom icons.
Predefined entity types
An entity type is used to map the resource vertex to an icon.
Notes:
- An administrator user can create more custom resource or entity types as required. Any observer may add new types.
- The topology service API only returns the resource or entity types in use.
To assign an entityType
- Select a resource with the provided entityType in the Topology Viewer.
- Select the topology tools (the cog icon), then navigate to the resource types.
- Find the type to be edited, and select the icon to assign it. You can find an icon either by name from the dropdown list, or by using the View all icons option (the eye icon).
Entity type icons
The following table lists these entity types with links to their icons, if defined:
Entity type | Icon |
---|---|
aircond | ![]() |
alarm | ![]() |
application | ![]() |
backplane | ![]() |
bridge | ![]() |
building | ![]() |
bypass | ![]() |
card | ![]() |
cell | ![]() |
channel | ![]() |
chassis | ![]() |
circuit | ![]() |
cluster | ![]() |
command | ![]() |
component | ![]() |
computer | ![]() |
container | ![]() |
cpu | ![]() |
credential | ![]() |
daemonset | ![]() |
database | ![]() |
datacenter | ![]() |
deployment | ![]() |
device | ![]() |
directory | ![]() |
disk | ![]() |
domain | ![]() |
emailaddress | ![]() |
environment | ![]() |
event | ![]() |
fan | ![]() |
file | ![]() |
firewall | ![]() |
flavor | ![]() |
forum | ![]() |
fqdn | ![]() |
gauge | ![]() |
group | ![]() |
host | ![]() |
hsrp | ![]() |
hub | ![]() |
image | ![]() |
input | ![]() |
ipaddress | ![]() |
ipam | ![]() |
loadbalancer | ![]() |
location | ![]() |
memory | ![]() |
message | ![]() |
namespace | ![]() |
network | ![]() |
networkaddress | ![]() |
networkgear | ![]() |
networkinterface | ![]() |
operatingsystem | ![]() |
organization | ![]() |
outlet | ![]() |
output | ![]() |
patch | ![]() |
path | ![]() |
pdu | ![]() |
peripherals | ![]() |
person | ![]() |
pod | ![]() |
printer | ![]() |
process | ![]() |
product | ![]() |
project | ![]() |
psu | ![]() |
resource | ![]() |
router | ![]() |
routetable | ![]() |
routetarget | ![]() |
rsm | ![]() |
rule | ![]() |
sector | ![]() |
securitygroup | ![]() |
sensor | ![]() |
server | ![]() |
service | ![]() |
serviceaccesspoint | ![]() |
slot | ![]() |
snmpsystem | ![]() |
stack | ![]() |
statefulset | ![]() |
status | ![]() |
storage | ![]() |
subnet | ![]() |
subscription | ![]() |
switch | ![]() |
swarm | ![]() |
task | ![]() |
tcpudpport | ![]() |
template | ![]() |
tenant | ![]() |
tier | ![]() |
tool | ![]() |
ups | ![]() |
variable | ![]() |
version | ![]() |
vlan | ![]() |
vm | ![]() |
volume | ![]() |
vpn | ![]() |
vrf | ![]() |
workload | ![]() |