Re: [Hawkular-dev] agent using custom metric IDs
+1
In general, id should be treated more from an abstract thing.
At the end, bringing some knowledge about how the id is built is a bad thing.
It is a technical debt that now we are suffering in MiQ and at some point we need to
address.
id should we similar as an UUID, IMO, nothing that you should use to extract business
info, for that we can include additional properties as Mike comments.
----- Mensaje original -----
De: "Michael Burman" <miburman(a)redhat.com>
Para: "John Mazzitelli" <mazz(a)redhat.com>, "Discussions around
Hawkular development" <hawkular-dev(a)lists.jboss.org>
Enviados: Viernes, 8 de Julio 2016 10:52:39
Asunto: Re: [Hawkular-dev] agent using custom metric IDs
Hi,
Why? The metricId is an id to a computer. It should not have anything
meaningful to the user. Use tags if you want some information to the stored
id. Stop pushing "structure" to the metricId, you can't use it for
searching
them.
- Micke
----- Original Message -----
From: "John Mazzitelli" <mazz(a)redhat.com>
To: hawkular-dev(a)lists.jboss.org
Sent: Friday, July 8, 2016 12:31:14 AM
Subject: Re: [Hawkular-dev] agent using custom metric IDs
> What if you used the inventory's canonical path as an the metric ID
Well, that doesn't solve the problem. That would just be replacing one
auto-generated ID for another one. The requirement is to allow a user to be
able to customize the metric ID to something the user wants. See the JIRA
for details: https://issues.jboss.org/browse/HWKAGENT-78
_______________________________________________
hawkular-dev mailing list
hawkular-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hawkular-dev
_______________________________________________
hawkular-dev mailing list
hawkular-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hawkular-dev