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

Add more logging to PR builds to trace lost messages #18206

Closed
churik opened this issue Dec 15, 2023 · 0 comments · Fixed by status-im/status-go#4494 or #18253
Closed

Add more logging to PR builds to trace lost messages #18206

churik opened this issue Dec 15, 2023 · 0 comments · Fixed by status-im/status-go#4494 or #18253
Assignees
@siddarthkay
Labels
message-reliability

Comments

@churik
Copy link
Member

churik commented Dec 15, 2023 •
edited
Loading

Problem

Currently, retrieving the message-id from the logs is not a straightforward process. As a result, there are no simple methods available to trace a specific message within the message history.

This issue was highlighted during the message reliability meeting, emphasizing the need to streamline the tracing of a particular message using its unique id.

Acceptance criteria

To address this problem, the following steps will be taken:

  1. Implement the necessary logging on the DEBUG level to facilitate easier debugging.
  2. This enhanced logging functionality will simplify the process of tracing and debugging specific messages from the logs, i.e. from: Data delivery issues #18031 only for e2e and PR builds

By fulfilling these acceptance criteria, we aim to improve the efficiency and effectiveness of message tracing within the application.
@churik churik changed the title Add more logging to PR build to trace lost messages Add more logging to PR builds to trace lost messages Dec 15, 2023
@siddarthkay siddarthkay self-assigned this Dec 16, 2023
@siddarthkay siddarthkay mentioned this issue Dec 20, 2023
Merged
siddarthkay added a commit to status-im/status-go that referenced this issue Dec 20, 2023
@siddarthkay
chore: log message contents before being sent
a02b480 
When debugging message reliability we often get the number of messages sent and their IDs but we do not know the content of the messages and the type of message sent.

This commit adds debug level logs so that it helps in investigations.

ref : status-im/status-mobile#18031

Closes [#18206](status-im/status-mobile#18206)
siddarthkay added a commit to status-im/status-go that referenced this issue Dec 20, 2023
@siddarthkay
chore: log message contents before being sent
25021bd 
When debugging message reliability we often get the number of messages sent and their IDs but we do not know the content of the messages and the type of message sent.

This commit adds debug level logs so that it helps in investigations.

ref : status-im/status-mobile#18031

Closes [#18206](status-im/status-mobile#18206)
@siddarthkay siddarthkay mentioned this issue Dec 20, 2023
Merged
siddarthkay added a commit to status-im/status-go that referenced this issue Dec 20, 2023
@siddarthkay
chore: log message contents before being sent
10ff9db 
When debugging message reliability we often get the number of messages sent and their IDs but we do not know the content of the messages and the type of message sent.

This commit adds debug level logs so that it helps in investigations.

ref : status-im/status-mobile#18031

Closes [#18206](status-im/status-mobile#18206)
siddarthkay added a commit to status-im/status-go that referenced this issue Dec 21, 2023
@siddarthkay
chore: log message contents before being sent
b8bb6e3 
When debugging message reliability we often get the number of messages sent and their IDs but we do not know the content of the messages and the type of message sent.

This commit adds debug level logs so that it helps in investigations.

ref : status-im/status-mobile#18031

Closes [#18206](status-im/status-mobile#18206)
siddarthkay added a commit to status-im/status-go that referenced this issue Dec 22, 2023
@siddarthkay
chore: log message contents before being sent
1bbc702 
When debugging message reliability we often get the number of messages sent and their IDs but we do not know the content of the messages and the type of message sent.

This commit adds debug level logs so that it helps in investigations.

ref : status-im/status-mobile#18031

Closes [#18206](status-im/status-mobile#18206)
siddarthkay added a commit to status-im/status-go that referenced this issue Dec 22, 2023
@siddarthkay
chore: log message contents before being sent
657895b 
When debugging message reliability we often get the number of messages sent and their IDs but we do not know the content of the messages and the type of message sent.

This commit adds debug level logs so that it helps in investigations.

ref : status-im/status-mobile#18031

Closes [#18206](status-im/status-mobile#18206)
siddarthkay added a commit to status-im/status-go that referenced this issue Dec 23, 2023
@siddarthkay
chore: log message contents before being sent
6c0ea61 
When debugging message reliability we often get the number of messages sent and their IDs but we do not know the content of the messages and the type of message sent.

This commit adds debug level logs so that it helps in investigations.

ref : status-im/status-mobile#18031

Closes [#18206](status-im/status-mobile#18206)
siddarthkay added a commit to status-im/status-go that referenced this issue Dec 23, 2023
@siddarthkay
chore: log message contents before being sent
9afc5cc 
When debugging message reliability we often get the number of messages sent and their IDs but we do not know the content of the messages and the type of message sent.

This commit adds debug level logs so that it helps in investigations.

ref : status-im/status-mobile#18031

Closes [#18206](status-im/status-mobile#18206)
siddarthkay added a commit to status-im/status-go that referenced this issue Dec 23, 2023
@siddarthkay
chore: log message contents before being sent
9bb691d 
When debugging message reliability we often get the number of messages sent and their IDs but we do not know the content of the messages and the type of message sent.

This commit adds debug level logs so that it helps in investigations.

ref : status-im/status-mobile#18031

Closes [#18206](status-im/status-mobile#18206)
siddarthkay added a commit to status-im/status-go that referenced this issue Dec 23, 2023
@siddarthkay
chore: log message contents before being sent (#4494)
151185c 
When debugging message reliability we often get the number of messages sent and their IDs but we do not know the content of the messages and the type of message sent.

This commit adds debug level logs so that it helps in investigations.

ref : status-im/status-mobile#18031

Closes [#18206](status-im/status-mobile#18206)
@ilmotta ilmotta removed the bug label Oct 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@siddarthkay siddarthkay

Labels
message-reliability
Projects
None yet
Milestone
No milestone
3 participants
@ilmotta @churik @siddarthkay