-
Notifications
You must be signed in to change notification settings - Fork 25
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
logs: improve Lure tracing #4342
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's double check that PostHog token, but otherwise looking good!
Sorry to expand scope, but could we add one last bit:
- From
%reel
log an Invite Link Created event when it receives%reel-confirmation
from the Provider (include token and flag) - From
%reel
log an Invite Link Removed event when it receives%reel-undescribe
(include token and flag)
Re Posthog token. If it the key is on the ship, the user can just read it, no matter where we put it. If want to do anything about it we would have to setup a logging service somewhere. |
@arthyn @latter-bolden Just in case you missed it, there is also a sibling PR in the landscape repo: tloncorp/landscape#304 |
Thanks. @arthyn and @latter-bolden obviously this is of critical importance to get out to livenet early next week. Thanks for your expedient reviews. :) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the clarification and fixes!
Arbitrary JSON data can now be supplied with a %logs report.
Taking advantage of this, Lure tracing in %grouper is improved.