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

Custom logging #670

Open
sparkacus opened this issue Dec 29, 2023 · 0 comments
Open

Custom logging #670

sparkacus opened this issue Dec 29, 2023 · 0 comments

Comments

@sparkacus
Copy link

Unless the source of the request retains data relating to a webhook, it can be tricky to identify why rules are not matched without enabling debug mode.

Would it be possible to support some form of custom logging that can output specific data? e.g. :

  • parm in the hook rules to enable logging for specific values
  • parm in the definition to log all values defined within the hook rules
  • parm in the definition that allows us to selectively define what values to log (regardless of rules)
[webhook] 2023/12/29 12:00:01 [652810] incoming HTTP POST request from {IP}:{PORT}
[webhook] 2023/12/29 12:00:01 [652810] slack got matched
[webhook] 2023/12/29 12:00:01 [652810] slack got matched, but didn't get triggered because the trigger rules were not satisfied
[webhook] 2023/12/29 12:00:01 [652810] 200 | 30 B | 266.65µs | {HOST} | POST /hooks/slack

[webhook] 2023/12/29 12:00:01 [652810] {CUSTOM LOGGING}
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants