Toni Tauro

TBH this looks more like a configuration issue. I have the same problem. Looking into it, probably opensearch is either missing a configuration option or even the [prometheus-exporter-plugin](https://github.com/Aiven-Open/prometheus-exporter-plugin-for-opensearch)

Looking at what port is by default configured (`9600`) I'd think the idea is to use the performance analyzer which is already included and installed as plugin on the opensearch...

Okay, when trying to start it inside the container I just see that the address is already bound but not reachable. I'm gonna continue troubleshoot this. ``` sh-5.2$ OPENSEARCH_HOME=/usr/share/opensearch/ OPENSEARCH_JAVA_HOME=/usr/share/opensearch/jdk/...

According to the initial PR, the SM is meant to be used in conjunction with https://github.com/Aiven-Open/prometheus-exporter-plugin-for-opensearch I'll try to integrate it and make sure it's installed by default when enabling...

You can configure the port with `metricsPort`

Related #593 and #594

@muhammeddanish yes see #593 We got prom metrics running with that plugin.

@pree what are your thoughts? Shouldn't we also have at least a critical one when tokencreation is massive and getting out of hands?

Have you tried setting: ``` controller: enableAnnotationValidations: false ``` **ATTENTION** tthis does not validate the annotaation anymore and let's sth like $redirect_uri in there through, but it could potentially brake...

Thanks @sicoyle The first step will to look if it works with the Vault provider and add that to the docs (pretty sure it does) Anyhow on the long run...