Codecov Report

Merging #63 (a584c61) into main (290ca60) will increase coverage by 0.60%. The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main      #63      +/-   ##
==========================================
+ Coverage   87.19%   87.79%   +0.60%     
==========================================
  Files          16       16              
  Lines         734      721      -13     
  Branches       70       68       -2     
==========================================
- Hits          640      633       -7     
+ Misses         72       66       -6     
  Partials       22       22

Impacted Files	Coverage Δ
numaprom/entities.py	`96.66% <ø> (-0.21%)`	:arrow_down:
numaprom/udf/inference.py	`100.00% <ø> (ø)`
numaprom/udf/postprocess.py	`90.00% <ø> (ø)`
numaprom/udf/preprocess.py	`100.00% <ø> (ø)`
numaprom/__init__.py	`76.92% <100.00%> (+1.92%)`	:arrow_up:
numaprom/tools.py	`86.95% <100.00%> (+3.75%)`	:arrow_up:
numaprom/udf/window.py	`94.23% <100.00%> (ø)`
numaprom/udsink/train.py	`92.40% <100.00%> (ø)`
numaprom/udsink/train_rollout.py	`84.04% <100.00%> (ø)`

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

sarabala1979 commented 1 year ago

Is it possible to have env variable to control the logs like info(default) if we want DEBUG level, we can set env DEBUG=true or LOG_LEVEL=debug ?

Is it possible in Python?

ab93 commented 1 year ago

Is it possible to have env variable to control the logs like info(default) if we want DEBUG level, we can set env DEBUG=true or LOG_LEVEL=debug ?

Is it possible in Python?

It is possible, and we do it currently

numaproj / numalogic-prometheus

fix: profile logging (v0.1.3) #63

Codecov Report