The service dependency views are driven by tags that correspond to pre-selected AWS or Azure tags.

You can change which AWS/Azure tags are used to create tagviews on the Admin Panel, under the Tag Views tab:


You can also reach this page via: https://{yourip}/#/admin/tagview


From here you can add and remove keys that correspond to resource tag names.

By default Hyperglance looks for tags named Application, Function, Owner and Service.


For example a resource might have a tag named Application:



Since 'Application' is set as a Tag View Key it will now show up as one of the views in the Views dropdown on the Diagram page: