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

Write detailed log messages from write failures in edge data replication #24481

Closed
davidby-influx opened this issue Nov 23, 2023 · 0 comments
Closed
Assignees

Comments

@davidby-influx
Copy link
Contributor

To assist debugging of write failures
in Edge Data Replication, do not
write only the HTTP status code to
the log. Also include any messages
returned by the write recipient.

@davidby-influx davidby-influx self-assigned this Nov 23, 2023
davidby-influx added a commit that referenced this issue Nov 23, 2023
To assist debugging of write failures
in Edge Data Replication, do not
write only the HTTP status code to
the log. Also include any messages
returned by the write recipient.

closes #24481
davidby-influx added a commit that referenced this issue Nov 30, 2023
To assist debugging of write failures
in Edge Data Replication, do not
write only the HTTP status code to
the log. Also include any messages
returned by the write recipient.

closes #24481
davidby-influx added a commit that referenced this issue Nov 30, 2023
To assist debugging of write failures
in Edge Data Replication, do not
write only the HTTP status code to
the log. Also include any messages
returned by the write recipient.

closes #24481

(cherry picked from commit 0ccd35c)

closes #24482
davidby-influx added a commit that referenced this issue Nov 30, 2023
To assist debugging of write failures
in Edge Data Replication, do not
write only the HTTP status code to
the log. Also include any messages
returned by the write recipient.

closes #24481

(cherry picked from commit 0ccd35c)

closes #24482
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

1 participant