The Wayback Machine - https://web.archive.org/web/20220430040813/https://github.com/topics/log-management
Skip to content
#

log-management

Here are 55 public repositories matching this topic...

gimmic
gimmic commented Sep 27, 2019

I have noticed when ingesting backlog(older timestamped data) that the "Messages per minute" line graph and "sources" data do not line up.

The Messages per minute appear to be correct for the ingest rate, but the sources breakdown below it only show messages for each type from within the time window via timestamp. This means in the last hour if you've ingested logs from 2 days ago, the data is

Wernfried
Wernfried commented Oct 12, 2020

I have an application which receives log messages from a firewall. The logs are written into a MongoDB. My goal is to process 30'000 messages per second (more or less constantly for 7*24 hours, not as transient peak value)
As peak value I expect app. 50'000 messages per second.

With several settings I reached up to 20'000 msg/sec. but that is not sufficient for our life traffic. The MongoDB ho

quickwit
guilload
guilload commented Apr 20, 2022
  • Remove data-dir option when not necessary
  • Fix the display order of some commands (1. config, 2. index, 3. source/split, 4. other options)
  • Make required options such as config or index actually required
  • Add aliases (ls, rm, ...) whenever possible
bug good first issue

Improve this page

Add a description, image, and links to the log-management topic page so that developers can more easily learn about it.

Curate this topic

Add this topic to your repo

To associate your repository with the log-management topic, visit your repo's landing page and select "manage topics."

Learn more