<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Oct 31, 2016, at 3:39 AM, Heiko W.Rupp <<a href="mailto:hrupp@redhat.com" class="">hrupp@redhat.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class="">
<meta http-equiv="Content-Type" content="text/xhtml; charset=utf-8" class="">
<div class="">
<div style="font-family:sans-serif" class=""><div style="white-space:normal" class=""><p dir="auto" class="">Hey,</p><p dir="auto" class="">we have labels in Hawkular-metrics right now, but apparently there are<br class="">
use cases that are not yet covered (and I know Matt has more)</p>
<ul class="">
<li class="">Listing keys of tags. Currently one has to know the available keys to be able to list the available values</li>
<li class="">tag values are currently a comma-separated string and not an array, which may have implications on allowed characters and escaping of separators</li>
<li class="">Post-tagging of data points (tagging could be provoked by another system that e.g. parses log files and sees an anomaly)
The idea behind it is that one should be able to create tags at certain points in time for a single metric or a list of metrics to uniquely identify that point in time for queries (relative performance of two versions of a deployment).</li></ul></div></div></div></div></blockquote><div>Data points are immutable by design. Once a row is written it is never updated. This allows for optimizations with compaction and deletions. We need to take that into consideration with post-tagging. Using a different table or tables might be a better option.</div></div></body></html>