At this point you are only able to specify one configuration setting for HostMetadataItem.

It would be handy if you were able to specify multiple items such as:

• HostMetadataItem=Hostname, system.hostname
• HostMetadataItem=Chassis, system.hw.chassis
• HostMetadataItem=OS, system.sw.os[name]
• HostMetadataItem=Architecture, system.sw.arch

Perhaps the format could be 'HostMetadataItem=<Label>,<Item>'  (i.e. HostMetadataItem=Hostname, system.hostname) so the data returned may look something like 'Hostname=HostX, Chassis=VMware Virtual Platform....'.

This way you would be able to tell what is what in the metadata returned and use this accordingly in the Auto-Registration actions when comparing values.

I would also suggest In addition if the agent could have a configuration setting to send metadata formatted as a JSON dict to contain these for example:

{     "Hostname": "HostX",     "Chassis": "VMware Virtual Platform",     "OS": "Red Hat Enterprise Linux Server 7.9 (Maipo)",     "Architecture": "x64" }

In the Auto-Registration actions it would be handy to have a compare/match/exists against a JSONPath so you can extract out specific values etc...

The use case is we currently have a script that produces metadata in the format of the following:

'0:<provider>,1:<client>,2:<group>,3:<agentType>,4:<agentVersion>,5:<agentListenIp>,6:<agentPort>,7:<host>,8:<hostFQDN>,9:<osFamily>,10:<osName>,11:<osBuild>,12:<architecture>'

This makes it easier to apply specific 'base' templates at the time of Agent Auto-Registration.