Add FATAL trace when alarms are released - MQTT

[mapedraza]

Component

When the following logs:

time=2024-10-04T07:45:15.835Z | lvl= | corr=de0bd7ec-72fc-44db-8040-1c2d79138a2d | trans=de0bd7ec-72fc-44db-8040-1c2d79138a2d | op=IOTAJSON.MQTT.Binding | from=n/a | srv=n/a | subsrv=n/a | msg=GLOBAL-002: Couldn't connect with MQTT broker: XXXX | comp=IoTAgent

Is your feature request related to a problem? Please describe

No response

Describe the solution you'd like

No response

Describe alternatives you've considered

No response

The systemd version you checked that didn't have the feature you are asking for

No response

[fgalan]

FATAL is normally used for errors that break the IOTA (i.e. the IOTA process stops). Why don't use ERROR (the usual level for errors) in this case?

[AlvaroVega]

Just here https://github.com/telefonicaid/iotagent-json/blob/dd6ebde6d4afe0f4c768af2937b5c48f2f73b3c4/lib/bindings/MQTTBinding.js#L266-L269

Some log like:

time=2024-10-02T12:36:06.432Z | lvl=ERROR | corr=b747e40a-b533-4f18-a736-f421b8a5d63f | trans=n/a | op=app | ver=3.0.0-next | ob=ES | comp=Urbo2 | msg=Releasing alarm MONGODB