entityID in JSON metrics?

[Paul Caskey]

> From: users [mailto:users-bounces at shibboleth.net] On Behalf Of Cantor,
> Scott
> 
> On 12/16/16, 4:52 PM, "users on behalf of Paul Caskey" <users-
> bounces at shibboleth.net on behalf of pcaskey at internet2.edu> wrote:
> 
> >    It would sure help to have that when attempting to process data
> > from multiple IdPs (especially when using http reporting).
> 
> I think it would be more appropriate to come at this from the point of view of
> a dedicated identifier that is obviously going to *be* the entityID in 99.9% of
> cases, but is formally speaking something specific to the problem and could
> be overridden to be something else if the actual entityID is not stable.
> 
> Or it could just be whatever the property is set to of course with the
> stipulation that it doesn't mean the IdP ever actually names itself that in a
> message.
> 

Thanks!

If I understand correctly, I could add a custom property in idp.properties (metrics.reporter.id) and just use that (default setting would be %{idp.entityID}) .  That is, of course, what I'm after - a reporting ID.  

So, is there a way of getting that custom property to show up in the JSON output?  All I'm seeing are custom timers and counters and this would be a gauge like the others, right?