telefonicaid / telefonicaid/iotagent-node-lib
Add FATAL trace when alarms are released - MQTT
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 62
- Forks
- 90
- Avg merge
- 2h 35m
- Merged PRs (30d)
- 1
Description
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
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the MQTT binding code that emits the GLOBAL-002 connection log and the path where alarms are released. Confirm the intended FATAL trace content and trigger conditions with maintainers; done means the trace is emitted reliably when an alarm is released and the relevant behavior is covered by existing checks.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- backend, networking
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100