topic Re: 'Environment' did not survive a reboot for a gateway on which I applied a JHF - is this expected in OpenTelemetry/Skyline

'Environment' did not survive a reboot for a gateway on which I applied a JHF - is this expected?

eth4_ — Tue, 27 Aug 2024 00:06:49 GMT

Recently applied a JHF to the stand by member of a cluster (R81.20). I was startled I didn't see telemetry coming in after enough time had passed for the reboot so I check the environment drop down and found 'Default' there - along with the missing gateway. Is there a way to make the setting survive a reboot?

Re: 'Environment' did not survive a reboot for a gateway on which I applied a JHF - is this expected

Chris_Atkinson — Tue, 27 Aug 2024 08:38:30 GMT

Could you please share additional specifics of the JHF used before & after etc?

Possibly this is one of those things more readily worked through with TAC via a remote session...

Re: 'Environment' did not survive a reboot for a gateway on which I applied a JHF - is this expected

Ruan_Kotze — Tue, 27 Aug 2024 13:39:47 GMT

Have experienced the same issue accross a couple of environments, but it seem random. Fix is always the same (do the below on the appliances not checking in):

Recreate payload-no-tls.json
Run "/opt/CPotelcol/REST.py --set_open_telemetry "$(cat payload-no-tls.json)"

Thanks,
Ruan

Re: 'Environment' did not survive a reboot for a gateway on which I applied a JHF - is this expected

the_rock — Tue, 27 Aug 2024 14:52:26 GMT

I can confirm 100% what @Ruan_Kotze said is indeed true. I had CP esc. guy send the same via case last year for this issue.

Best,

Andy