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.

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

Structured logging of message fetching and delivery #76

Closed
tpitale opened this issue Jun 17, 2016 · 3 comments
Closed

Structured logging of message fetching and delivery #76

tpitale opened this issue Jun 17, 2016 · 3 comments

Comments

@tpitale
Copy link
Owner

tpitale commented Jun 17, 2016

It may be valuable to know that messages are being fetched/processed/delivered to a remote location in a structured log. Still undecided on this. If using que/sidekiq new jobs will be processed; if using logger all messages are already logged. Only in a remote delivery case (callbacks) would it be especially hard to know if new messages were being fetched/delivered without a log if the remote service is not within the users control.

@tpitale
Copy link
Owner Author

tpitale commented Jun 17, 2016

This also makes me think about other instrumentation like timing and stats into influxdb or something.

With structured logs we could consume the log and send stats as a distinct process. Or ship the right off to log processing tools to be analyzed.

@cablett
Copy link
Collaborator

cablett commented Sep 19, 2019

Hi @tpitale ! I started a PR continuing @ZJvandeWeg 's earlier work on structured logging. What do you think?

@tpitale
Copy link
Owner Author

tpitale commented Sep 26, 2019

Resolved in #88.

@tpitale tpitale closed this as completed Sep 26, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants