Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Tracing/monitoring #98

Open
briggySmalls opened this issue Dec 23, 2020 · 2 comments
Open

Tracing/monitoring #98

briggySmalls opened this issue Dec 23, 2020 · 2 comments

Comments

@briggySmalls
Copy link
Owner

The events leaading to #97 have revealed a need for some event monitoring. There is currently no too way to review historic MQTT events, or trace them to SQS events.

To retrospectively diagnose issues this should be introduced.
@briggySmalls
Copy link
Owner Author

I've turned on AWS logging but I wonder if there is something better that could be done

@briggySmalls
Copy link
Owner Author

For the time-being, tracing from MQTT to SQS could be done via the "timestamp" property. This wouldn't scale to many customers, but given I have...ahem...one. That's fine

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@briggySmalls