crowdsec: remove warning if prometheus port is taken during cold logs processing #2857
Conversation
|
@mmetc: There are no 'kind' label on this PR. You need a 'kind' label to generate the release automatically.
DetailsI am a bot created to help the crowdsecurity developers manage community feedback and contributions. You can check out my manifest file to understand my behavior and what I can do. If you want to use this for your project, you can check out the BirthdayResearch/oss-governance-bot repository. |
|
@mmetc: There are no area labels on this PR. You can add as many areas as you see fit.
DetailsI am a bot created to help the crowdsecurity developers manage community feedback and contributions. You can check out my manifest file to understand my behavior and what I can do. If you want to use this for your project, you can check out the BirthdayResearch/oss-governance-bot repository. |
mmetc
added
kind/enhancement
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #2857 +/- ##
==========================================
+ Coverage 57.98% 58.00% +0.01%
==========================================
Files 240 240
Lines 31040 31042 +2
==========================================
+ Hits 18000 18005 +5
+ Misses 11411 11408 -3
Partials 1629 1629
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
...to avoid port conflict warning, also change "acquisition is finished" to Info
mmetc
force-pushed
the
disable-oneshot-metrics
branch
from
93726d0
to
19e5fdc
Compare
mmetc
changed the title
this removes a Warning log because likely LAPI is behind it