You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, I am trying to setup a sidecar exporter with docker.
The sidecar exporter with initial setting is deployed successfully, and I received message when I visit the page hostname:8086
Current Configuration
hostName: hostname
port: 7001
queries:
I tried to update the configuration with curl command curl -X PUT -i -u wlsusername:wlspassword -H "content-type: application/yaml" --data-binary "@./wlsexporter_conf.yaml" http://hostname:8086/configuration
and I received
but nothing in the site hostname:port changes, and I am getting the same message as shown in the first code block. So I wonder what could be the reason for this failure. The configuration file that I am trying to upload is
Hi, I have been able to setup the exporter successfully. While I am not sure why the above issue happened, I did succeeded in uploading the configuration and working with the exporter.
Hi, I think I found the cause of the issue. So my site is running in http mode but I create the container with -DWLS_SECURE=true. In this case when I try to upload the configuration file, it fails but still gives 200 response. Is there a way to make the exporter support the connection type check?
Hi, I am trying to setup a sidecar exporter with docker.
The sidecar exporter with initial setting is deployed successfully, and I received message when I visit the page hostname:8086
I tried to update the configuration with curl command
curl -X PUT -i -u wlsusername:wlspassword -H "content-type: application/yaml" --data-binary "@./wlsexporter_conf.yaml" http://hostname:8086/configuration
and I received
but nothing in the site hostname:port changes, and I am getting the same message as shown in the first code block. So I wonder what could be the reason for this failure. The configuration file that I am trying to upload is
The text was updated successfully, but these errors were encountered: