Rationale for not having the JSON format is that metrics implementations such as Micrometer and Open Telemetry Metrics have their own exporters...
As you can see from https://micrometer.io/docs/concepts#_supported_monitoring_systems , Micrometer already supports a lot of different backends (AppOptics, Atlas, Azure Monitor, Cloudwatch, Datadog, Datadog StatsD, Dynatrace, Elastic, Humio, Influx, KairosDB, New Relic, Prometheus, SignalFx, Sysdig StatsD, Telegraf StatsD, Wavefront, Graphite, Ganglia, JMX, Etsy StatsD) , so the question is whether you'd want a JSON-formatted REST endpoint in addition to the list Micrometer already has support for.
Rationale for not having the JSON format is that metrics implementations such as Micrometer and Open Telemetry Metrics have their own exporters...
As you can see from https://micrometer.io/docs/concepts#_supported_monitoring_systems , Micrometer already supports a lot of different backends (AppOptics, Atlas, Azure Monitor, Cloudwatch, Datadog, Datadog StatsD, Dynatrace, Elastic, Humio, Influx, KairosDB, New Relic, Prometheus, SignalFx, Sysdig StatsD, Telegraf StatsD, Wavefront, Graphite, Ganglia, JMX, Etsy StatsD) , so the question is whether you'd want a JSON-formatted REST endpoint in addition to the list Micrometer already has support for.
had a discussion in MicroProfile forum (https://groups.google.com/g/microprofile/c/rsks3oyGJEU ) - no objections raised (though almost nobody replied).