<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Now that we have switched to Resource Paths (canonical paths from Inventory) it has come up that displaying the resource path is not very readable and requires parsing to make sense of it.<div class=""><br class=""></div><div class="">Please see the current use case as example:</div><div class=""><a href="https://issues.jboss.org/secure/attachment/12392747/AlertCenter2.jpg" class="">https://issues.jboss.org/secure/attachment/12392747/AlertCenter2.jpg</a></div><div class=""><a href="https://issues.jboss.org/secure/attachment/12392582/Alert-detailsnu.jpg" class="">https://issues.jboss.org/secure/attachment/12392582/Alert-detailsnu.jpg</a></div><div class=""><br class=""><div class=""><br class=""><div class="">An example resource path:</div><div class="">/t;28026b36-8fe4-4332-84c8-524e173a68bf/e;test/f;localhost/r;localhost~Local~~</div><div class=""><br class=""></div><div class="">To further break the above example into its pieces:</div><div class=""><b class="">tenantId</b>: /t;28026b36-8fe4-4332-84c8-524e173a68bf</div><div class=""><b class="">environment</b>: test</div><div class=""><b class="">feed</b>: localhost</div><div class=""><b class="">resourceId</b>: localhost</div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""></div><div class="">The following snippet explaining the resource path was extracted from: <a href="http://www.hawkular.org/docs/components/inventory/index.html" class="">http://www.hawkular.org/docs/components/inventory/index.html</a></div><div class=""><br class=""></div><div class=""><dt class="hdlist1" style="box-sizing: border-box; line-height: 1.42857; font-weight: bold; margin-bottom: 0.3125em; color: rgb(72, 72, 72); font-family: 'Open Sans', sans-serif; font-size: 14px; widows: 1; background-color: rgb(255, 255, 255);">Canonical Paths</dt><dd style="box-sizing: border-box; line-height: 1.42857; margin-left: 1.125em; margin-bottom: 1.25em; color: rgb(72, 72, 72); font-family: 'Open Sans', sans-serif; font-size: 14px; widows: 1; background-color: rgb(255, 255, 255);" class=""><p style="box-sizing: border-box; margin: 0px 0px 10px; line-height: 1.5;" class="">A canonical path follows the <code style="box-sizing: border-box; font-family: Menlo, Monaco, Consolas, 'Courier New', monospace; font-size: 0.9375em; padding: 1px 3px 0px; color: rgb(199, 37, 78); white-space: nowrap; border-radius: 4px; border: 1px solid rgb(204, 204, 204); text-shadow: none; background-color: rgb(242, 242, 242);" class="">contains</code> relationships from a tenant down to the entity in question.</p><div class="paragraph" style="box-sizing: border-box;"><p style="box-sizing: border-box; margin: 0px 0px 10px; line-height: 1.5;" class="">The canonical path has a form illustrated by the following example:</p></div><div class="exampleblock" style="box-sizing: border-box;"><div class="content" style="box-sizing: border-box; border: 1px solid rgb(230, 230, 230); margin-bottom: 1.25em; padding: 1.25em; border-top-left-radius: 4px; border-top-right-radius: 4px; border-bottom-right-radius: 4px; border-bottom-left-radius: 4px; background-position: initial initial; background-repeat: initial initial;"><div class="paragraph" style="box-sizing: border-box; margin-top: 0px; margin-bottom: 0px;"><div style="box-sizing: border-box; margin: 0px; line-height: 1.5; color: rgb(51, 51, 51);" class=""><span style="box-sizing: border-box; font-weight: 600;" class="">/t;</span><em style="box-sizing: border-box;" class="">tenant-id</em><span style="box-sizing: border-box; font-weight: 600;" class="">/e;</span><em style="box-sizing: border-box;" class="">env-id</em><span style="box-sizing: border-box; font-weight: 600;" class="">/r;</span><em style="box-sizing: border-box;" class="">resource-id</em></div></div></div></div><div class="paragraph" style="box-sizing: border-box;"><p style="box-sizing: border-box; margin: 0px 0px 10px; line-height: 1.5;" class="">The above example is a canonical path to a resource with ID <code style="box-sizing: border-box; font-family: Menlo, Monaco, Consolas, 'Courier New', monospace; font-size: 0.9375em; padding: 1px 3px 0px; color: rgb(199, 37, 78); white-space: nowrap; border-radius: 4px; border: 1px solid rgb(204, 204, 204); text-shadow: none; background-color: rgb(242, 242, 242);" class="">resource-id</code> which is located in environment <code style="box-sizing: border-box; font-family: Menlo, Monaco, Consolas, 'Courier New', monospace; font-size: 0.9375em; padding: 1px 3px 0px; color: rgb(199, 37, 78); white-space: nowrap; border-radius: 4px; border: 1px solid rgb(204, 204, 204); text-shadow: none; background-color: rgb(242, 242, 242);" class="">env-id</code> which is inside a tenant <code style="box-sizing: border-box; font-family: Menlo, Monaco, Consolas, 'Courier New', monospace; font-size: 0.9375em; padding: 1px 3px 0px; color: rgb(199, 37, 78); white-space: nowrap; border-radius: 4px; border: 1px solid rgb(204, 204, 204); text-shadow: none; background-color: rgb(242, 242, 242);" class="">tenant-id</code>.</p></div><div class="paragraph" style="box-sizing: border-box;"><p style="box-sizing: border-box; margin: 0px 0px 10px; line-height: 1.5;" class="">The type specifiers in the individual path segments can be these:</p></div><div class="ulist" style="box-sizing: border-box;"><ul style="box-sizing: border-box; margin-top: 0px; margin-bottom: 10px; font-size: 1em; line-height: 1.6; list-style-position: outside; font-family: inherit; margin-left: 1.5em;" class=""><li style="box-sizing: border-box;" class=""><div style="box-sizing: border-box; margin: 0px 0px 0.625em; line-height: 1.5;" class=""><span style="box-sizing: border-box; font-weight: 600;" class="">t</span> - tenant</div></li><li style="box-sizing: border-box;" class=""><div style="box-sizing: border-box; margin: 0px 0px 0.625em; line-height: 1.5;" class=""><span style="box-sizing: border-box; font-weight: 600;" class="">e</span> - environment</div></li><li style="box-sizing: border-box;" class=""><div style="box-sizing: border-box; margin: 0px 0px 0.625em; line-height: 1.5;" class=""><span style="box-sizing: border-box; font-weight: 600;" class="">rt</span> - resource type</div></li><li style="box-sizing: border-box;" class=""><div style="box-sizing: border-box; margin: 0px 0px 0.625em; line-height: 1.5;" class=""><span style="box-sizing: border-box; font-weight: 600;" class="">mt</span> - metric type</div></li><li style="box-sizing: border-box;" class=""><div style="box-sizing: border-box; margin: 0px 0px 0.625em; line-height: 1.5;" class=""><span style="box-sizing: border-box; font-weight: 600;" class="">f</span> - feed</div></li><li style="box-sizing: border-box;" class=""><div style="box-sizing: border-box; margin: 0px 0px 0.625em; line-height: 1.5;" class=""><span style="box-sizing: border-box; font-weight: 600;" class="">r</span> - resource</div></li><li style="box-sizing: border-box;" class=""><div style="box-sizing: border-box; margin: 0px 0px 0.625em; line-height: 1.5;" class=""><span style="box-sizing: border-box; font-weight: 600;" class="">m</span> - metric</div><div class=""><br class=""></div></li></ul></div></dd></div><div class="">And as I understand it, the resource path also contains the parent resource prepended to this. So one can always figure out where the resource came from and can uniquely identify a resource.</div></div><div class="">A resource path is just one kind of canonical path (the others are given in the above except).</div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""></div><div class="">What fields should we parse out and display in the UI as individual fields?</div><div class=""><br class=""></div><div class="">I’ll start this conversation by assuming that the environment and tenant are not very useful to display. Then what about feed? And since resource is what we are after that one is obvious as needed.</div><div class="">WDYT?</div><div class=""><br class=""></div><div class="">And then there is the question of how Ancestry path should be viewed — <i class="">but for now lets just stick to the above question of how should resources be viewed in the UI?</i></div><div class=""><i class="">Ancestry Path is another topic for later.</i></div><div class=""><br class=""></div><div class=""><br class=""></div><div class="">Please refer to Jira: <a href="https://issues.jboss.org/browse/HAWKULAR-605" class="">https://issues.jboss.org/browse/HAWKULAR-605</a></div></div></body></html>