Release 3.0 sets jmix.ui.legacy-monitoring-enabled=true.
And then this is remarked as deprecated ?!
Is there somewhere any documentation what is the reason to set this and what we should do as it is deprecated ?
Best regards
Felix
Hi Felix,
Let me quote from Javadocs:
Whether to keep recording the legacy
io.micrometer.core.instrument.Timer-based UI metrics with their original tag schema. Currently controls jmix.ui.data (tags dataLoader/view/lifeCycle) and jmix.ui.views (tags view/lifeCycle). The same metric names are also produced by the modern Observation path with a different tag schema; this flag exists only for back-compat with dashboards built on the legacy tag set.Defaults to false in 3.0 — new projects start without the legacy Timer path. Set to true during a migration if you still have dashboards on the legacy tag schema, and drop the override once dashboards have moved to the modern schema. While both flags are true the modern Observation Timer-side for jmix.ui.* is suppressed by a MeterFilter so the two schemas don’t collide on registration; tracing spans are unaffected. See
io.jmix.flowui.observation.UiObservationSupport.Deprecated
Goes away together with UiMonitoring and LegacyUiTimerSupport once consumers have migrated to the modern Observation tag schema.
So it’s set to true in existing projects to not break monitoring dashboards if you have any.
Also, note that deprecated doesn’t mean dangerous or something. It will be deleted only in the next major version (4.0).
Regards,
Konstantin