Alfresco integration can be confusing about alfred-telemetry HOT 5 OPEN

@todorinskiz OOTB = Out Of The Box. Sorry for the confusion.

from alfred-telemetry.

I don't see a reason to depend on external modules (OOTB) - Alfresco already provides MicroMeter metrics, so we should be exposing those IMO.
There is also no need to provide any compatibility features with OOTB:

• Normally, all modules should use the same micrometer provided by the platform to avoid having multiple metrics registries
• Publishing / exposing the metrics should be provided as a separate module, to avoid dependency problems and to avoid having to be aware of all of the possible metrics registered - we only care about what is registered inside MicroMeter, right?

This way both Alfred Telemetry and OOTB can run in parallel, without influencing each other.

from alfred-telemetry.

In that case I would consider Alfresco as our central audience - let's expose our metrics to Alfresco by default.
This way we can make it easier for newcomers to start using it.

For other use cases that require reconfiguration for the monitoring system, seems reasonable to expect some learning curve there.

from alfred-telemetry.

cc @tgeens @thijslemmens what do you think?

from alfred-telemetry.

Better option is to remove complexity and just remove integration between OOTBox Alfresco metrics and Alfred Telemetry. Not try to magically integrate them.

from alfred-telemetry.