-
Notifications
You must be signed in to change notification settings - Fork 61
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
[MM-61122] Add diagnostics data to the Support Packet #904
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.
Thanks @hanzei . A couple of comments below.
Co-authored-by: Claudio Costa <[email protected]>
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.
Looks great, thanks!
@wiggin77 Gentle reminder to review the PR 😉 |
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.
Approved with minor change request.
Per discussion with @raghavaggarwal2308, QA testing will happen post-merge. |
Summary
When a Support Packet gets generated, the plugin now includes diagnostics data via a
diagnostics.yaml
file into the Packet.Example content of
com.mattermost.calls/diagnostics.yaml
:Requires mattermost/mattermost#28833 on the server side.
See https://mattermost.atlassian.net/wiki/spaces/CLOUD/pages/3083108354/Diagnostics+data+from+Core+Plugins+to+the+Support+Packet for more context.
Ticket Link
https://mattermost.atlassian.net/browse/MM-61122