Skip to content
This repository has been archived by the owner on Jan 15, 2024. It is now read-only.

EQS logs: get rid of alerts due to async-h1 error #1177

Open
sveitser opened this issue Jun 28, 2022 · 1 comment
Open

EQS logs: get rid of alerts due to async-h1 error #1177

sveitser opened this issue Jun 28, 2022 · 1 comment

Comments

@sveitser
Copy link
Contributor

sveitser commented Jun 28, 2022

Zulip thread. We don't know what causes the errors from but it does lead to noisy alerts. I think we should at least configure datadog to ignore it.

@sveitser sveitser changed the title EQS logs: handle async-h1 error EQS logs: get rid of alerts due to async-h1 error Jun 28, 2022
@sveitser
Copy link
Contributor Author

@Ancient123 added an exclusion for tide::listener::tcp_listener as a logger to trigger alerts. I think unless we want to investigate the cause we could close this.

It's however strange that we have been getting a lot more of these errors (the current rate is about 3000 per day) since we deployed the update yesterday.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant