search

ccin2p3 / samplerr

Round robin timeseries middleware based on riemann and elasticsearch
Eclipse Public License 1.0
15 stars 4 forks source link

Decrease verbosity #18

Closed smortex closed 1 year ago

smortex commented 4 years ago

The plugin logs a lot of information when everything is fine. Decrease the logging level of these informational messages.

The idea is to not have the following in riemann logs:

INFO [2020-06-09 21:30:02,148] defaultEventExecutorGroup-2-12 - riemann.plugin.samplerr - elasticized 1000  (total)  {201 1000}  docs to  .samplerr-2020.06.10 in  52 ms
INFO [2020-06-09 21:30:04,220] defaultEventExecutorGroup-2-8 - riemann.plugin.samplerr - elasticized 1000  (total)  {201 1000}  docs to  .samplerr-2020.06.10 in  90 ms
INFO [2020-06-09 21:30:05,282] defaultEventExecutorGroup-2-9 - riemann.plugin.samplerr - elasticized 1000  (total)  {201 1000}  docs to  .samplerr-2020.06.10 in  64 ms
INFO [2020-06-09 21:30:06,211] riemann task 1 - riemann.plugin.samplerr - elasticized 260  (total)  {201 260}  docs to  .samplerr-2020.06.10 in  42 ms
INFO [2020-06-09 21:30:16,298] riemann task 2 - riemann.plugin.samplerr - elasticized 596  (total)  {201 596}  docs to  .samplerr-2020.06.10 in  77 ms
INFO [2020-06-09 21:30:19,709] defaultEventExecutorGroup-2-11 - riemann.plugin.samplerr - elasticized 1000  (total)  {201 1000}  docs to  .samplerr-2020.06.10 in  122 ms
INFO [2020-06-09 21:30:22,278] defaultEventExecutorGroup-2-12 - riemann.plugin.samplerr - elasticized 1000  (total)  {201 1000}  docs to  .samplerr-2020.06.10 in  105 ms
INFO [2020-06-09 21:30:24,356] defaultEventExecutorGroup-2-8 - riemann.plugin.samplerr - elasticized 1000  (total)  {201 1000}  docs to  .samplerr-2020.06.10 in  57 ms
INFO [2020-06-09 21:30:25,435] defaultEventExecutorGroup-2-11 - riemann.plugin.samplerr - elasticized 1000  (total)  {201 1000}  docs to  .samplerr-2020.06.10 in  64 ms
INFO [2020-06-09 21:30:26,232] riemann task 2 - riemann.plugin.samplerr - elasticized 236  (total)  {201 236}  docs to  .samplerr-2020.06.10 in  58 ms
INFO [2020-06-09 21:30:36,257] riemann task 2 - riemann.plugin.samplerr - elasticized 596  (total)  {201 596}  docs to  .samplerr-2020.06.10 in  68 ms
INFO [2020-06-09 21:30:39,623] defaultEventExecutorGroup-2-2 - riemann.plugin.samplerr - elasticized 1000  (total)  {201 1000}  docs to  .samplerr-2020.06.10 in  87 ms
INFO [2020-06-09 21:30:42,221] defaultEventExecutorGroup-2-1 - riemann.plugin.samplerr - elasticized 1000  (total)  {201 1000}  docs to  .samplerr-2020.06.10 in  63 ms
INFO [2020-06-09 21:30:44,650] defaultEventExecutorGroup-2-11 - riemann.plugin.samplerr - elasticized 1000  (total)  {201 1000}  docs to  .samplerr-2020.06.10 in  87 ms
INFO [2020-06-09 21:30:45,525] defaultEventExecutorGroup-2-11 - riemann.plugin.samplerr - elasticized 1000  (total)  {201 1000}  docs to  .samplerr-2020.06.10 in  81 ms
INFO [2020-06-09 21:30:46,185] riemann task 2 - riemann.plugin.samplerr - elasticized 143  (total)  {201 143}  docs to  .samplerr-2020.06.10 in  16 ms
INFO [2020-06-09 21:30:56,265] riemann task 3 - riemann.plugin.samplerr - elasticized 550  (total)  {201 550}  docs to  .samplerr-2020.06.10 in  89 ms
INFO [2020-06-09 21:30:59,557] defaultEventExecutorGroup-2-7 - riemann.plugin.samplerr - elasticized 1000  (total)  {201 1000}  docs to  .samplerr-2020.06.10 in  42 ms
smortex commented 4 years ago

I see. On our side syslog-ng events are send to riemann which sends them to ElasticSearch, and we where not (yet) insane enough to introduce a loop in our setup (yet riemann can alert us when some nodes stops producing events).

Can you please detail what you mean by "when sending is failing"? Maybe we can find a way to make this logging accessible conditionally to fit all users our needs…

faxm0dem commented 4 years ago

I just meand that there is no "snake eats its own tail" loop when parsing the log data.