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

Remove error logs in processing loop #431

Merged
merged 1 commit into from
May 11, 2023

Conversation

jotak
Copy link
Member

@jotak jotak commented May 4, 2023

Errors are provided as metrics only to minimize the impact on resources, and logs readability, when an error is thrown repeatedly.

@codecov
Copy link

codecov bot commented May 4, 2023

Codecov Report

Merging #431 (7102b27) into main (95395fc) will decrease coverage by 0.02%.
The diff coverage is 33.33%.

@@            Coverage Diff             @@
##             main     #431      +/-   ##
==========================================
- Coverage   64.74%   64.72%   -0.02%     
==========================================
  Files          94       94              
  Lines        6651     6654       +3     
==========================================
+ Hits         4306     4307       +1     
- Misses       2102     2104       +2     
  Partials      243      243              
Flag Coverage Δ
unittests 64.72% <33.33%> (-0.02%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files Coverage Δ
pkg/pipeline/ingest/ingest_grpc.go 73.97% <0.00%> (-1.03%) ⬇️
pkg/pipeline/ingest/ingest_kafka.go 65.21% <42.85%> (-0.17%) ⬇️

@jpinsonneau
Copy link
Collaborator

Errors are provided as metrics only to minimize the impact on resources, and logs readability, when an error is thrown repeatedly.

I disagree with this approach especially at current project state. We should give qe and end users all the necessary info to identify bugs and help us to fix these.
If you don't want to impact resources, we can simply update these to debug or trace and document how to report a bug with a step including this change.

@jotak
Copy link
Member Author

jotak commented May 10, 2023

@jpinsonneau So we can indeed move the logs as "trace" or "debug" but the value is low since we discourage users from setting such as level, for performance reasons. QE also don't use that in perf tests. Metrics are really the best way to get these errors.

@jotak
Copy link
Member Author

jotak commented May 11, 2023

/approve

@openshift-ci
Copy link

openshift-ci bot commented May 11, 2023

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jotak

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-merge-robot openshift-merge-robot merged commit 12a8263 into netobserv:main May 11, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants