[Hawkular-dev] A convention for metrics (short) name

[Thomas Heute]

We definitely need to solve that usability issue, I definitely experienced
it in Grafana.

For Grafana in particular, I know Prometheus driver has a "label name" that
is defined in Grafana and can be templatized with metrics labels. It's
purely on Grafana side and only works for Grafana.

Having a convention is a quick solution, do we see it used by Metrics
internals or only by agents and UIs ? Does it need to support templating
with other tags or do we expect the client to be smarter to tags value
change ?

I would also suggest displayName (or display_name or else) rather than just
name, I think it's clearer that it's for UI and can change.




On Wed, Aug 9, 2017 at 10:53 AM, Heiko Rupp <hrupp at redhat.com> wrote:

> On 9 Aug 2017, at 8:41, Joel Takvorian wrote:
>
> > What would you say about having a convention of a special tag (let's
> > say "_name") that would point to a (short) intelligible name for a
> > metric. That convention wouldn't be mandatory in any case of course,
> > but the UI could check if that tag exists and use that name, instead
> > of the full metric id, for better display.
>
> Makes sense to me.
> We had a displayName in RHQ.
> _______________________________________________
> hawkular-dev mailing list
> hawkular-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hawkular-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/hawkular-dev/attachments/20170809/41fdba34/attachment.html