Christopher J. Morrone

I don't think anyone is suggesting the "Currently Non Requirements", so I think we're all good there. > Having a base structure that is overloaded to contain additional data for...

@baallan I do generally agree with all of that. I was alluding to the same thing when I questioned the semantics earlier. It looks like get_set() is something that is...

@baallan, please have that discussion in another ticket.

Multi-config could _almost_ solve it, because we can use different strgrps with different regex's to map to the different store configs. But strgrps regex only match LDMS schemas, not _decomposed_...

Either way, we would need to find a new place to set the sampler update hint (that happens under ldmsd_set_register).

Another usability issue with ldms and decomposition is that "ldms_ls" doesn't show the data type for any of the fields in a record in a list (maybe not in a...

>For static decomposition, the idea is that the user statically define the storage schema so that only the selected metrics that the user cares about are being stored. _Are_ we...

> @morrone, I played with some of the ideas you mentioned and have this implemented for static [cut] > In any event, is this more in line with what you...

Oh, what happens when "rec_member" is also supplied? Honestly, I would prefer that the rec_member name be the "dst" name any time there isn't a name conflict (as opposed to...

> it would be a trivial matter to add an option to ldmsd_controller or (better) ldms_ls that discovers the unique schemas within all existent sets and dumps the "default" static...