`metrics_instance` format hard to work with

[james-callahan]

trafficstars

When using the Operator, an Integration needs to know the name of the MetricsInstance it belongs to if it wants data to be emitted.

This is troublesome if I don't know the namespace my Integration will be deployed to ahead of time.

• Couldn't the metrics instance be figured out automatically?
• Why can't I set the name of the metrics instance my MetricsInstance creates so that I have a well-known name?
• Could you at least split the field into namespace and metrics instance name e.g. metrics_instance: { namespace: XYZ, name: my-metrics-instance} so that I can set the namespace easily

[marctc]

Hey @james-callahan, we tried to document use cases and how to work integrations with the operator here. Do you think is enough to understand how to use integration with operator?

[james-callahan]

@marctc I understand it, the problem is that it's difficult to use. The problem steps from metrics_instance: default/primary: which is in the format of <namespace>/<name of metrics instance>. It means the integration itself needs to know the namespace of where its MetricsInstance is.

[marctc]

I see, didn't know that actually. Would it help to clarify it that document? To be honest, I don't think we have bandwith to change that in near future.