You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am trying to use seq for my home server. Among other things I am forwarding docker logs via gelf to seq. To do this I use seq-input-gelf. My current rate of "idle" logging is 2 short messages/second. However I see that seq-input-gelf uses seqcli, which has an average 6% of CPU usage (xeon M1505). That seems excessively high from transferring ~500 bytes of data per second. Is such high CPU usage normal? How can I troubleshoot it?
The text was updated successfully, but these errors were encountered:
I believe this is due to the seq-input-gelf container using an older seqcli version. We're planning some maintenance on seq-input-gelf for the near future, so I'll move this ticket over to that repository.
I am trying to use seq for my home server. Among other things I am forwarding docker logs via gelf to seq. To do this I use seq-input-gelf. My current rate of "idle" logging is 2 short messages/second. However I see that seq-input-gelf uses seqcli, which has an average 6% of CPU usage (xeon M1505). That seems excessively high from transferring ~500 bytes of data per second. Is such high CPU usage normal? How can I troubleshoot it?
The text was updated successfully, but these errors were encountered: