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

Revisit INFO logs #214

Merged
merged 8 commits into from
Mar 27, 2024
Merged

Revisit INFO logs #214

merged 8 commits into from
Mar 27, 2024

Conversation

Siegrift
Copy link
Collaborator

@Siegrift Siegrift commented Mar 21, 2024

Closes #189
Closes #198

Rationale

The INFO logs logged very little. This is now changed because both "data fetching loop" and "update feeds loops" now log a message. I went through each log one-by-one and I updated the severity whenever I felt it's a good idea.

I also changed that we log the chain name instead of chain ID.

Copy link
Contributor

@bdrhn9 bdrhn9 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There are some suggestions below. Other than that LGTM 🔥

  • Here we can set log level to INFO, because it is similar to Deviation exceed. log above.
  • Here can be set to WARN.

src/utils.ts Outdated Show resolved Hide resolved
Base automatically changed from heatbeat to main March 27, 2024 18:10
@Siegrift
Copy link
Collaborator Author

Here can be set to WARN.

FYI, a bit related #218

@Siegrift Siegrift merged commit 72af392 into main Mar 27, 2024
4 checks passed
@Siegrift Siegrift deleted the better-logs branch March 27, 2024 18:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Log with chain alias instead of chain ID Revisit INFO logs
2 participants