ozone insight logs om.protocol.client always tries to connect to 0.0.0.0:9874

[mark-bb]

Hello.

Ozone 2.0.0

Whenever I try to use HTTPS in the ozone.http.policy (HTTPS_ONLY or HTTP_AND_HTTPS), the ozone insight logs om.protocol.client command returns an error ('Connection refused' or 'HTTP 401' respectively) with the org.apache.http.conn.HttpHostConnectException: Connect to 0.0.0.0:9874 [/0.0.0.0] failed message.

That is, my config looks like:

<property><name>ozone.http.policy</name><value>HTTPS_ONLY</value></property>
<property><name>ozone.om.https-address</name><value>0.0.0.0:9875</value></property>
<property><name>ozone.om.https-address.omservice1.host1</name><value>https://host1.internal:9875</value></property>
<property><name>ozone.om.https-address.omservice1.host2</name><value>https://host2.internal:9875</value></property>
<property><name>ozone.om.https-address.omservice1.host3</name><value>https://host3.internal:9875</value></property>

What should I do to make it work in a secured environment?

[errose28]

From looking at the code it looks like ozone insight does not support HTTPS. This is not a command that we have updated much since it was initially added in Ozone 0.5.0 and is not widely used as far as I know. I filed HDDS-13883 to add support for this in the future.

[jojochuang]

https://ozone.apache.org/docs/edge/feature/observability.html

Under the hood ozone insight uses HTTP endpoints to retrieve the required information (/conf, /prom and /logLevel endpoints). It’s not yet supported in secure environment.