Nagios Support Forum

When you’re digging through logs, sometimes the single matching line isn’t enough—you need the few entries before and after it to understand the full picture. Instead of manually narrowing down by host and time span, most tools give you a way to grab context lines automatically.
myccpay

This sounds like it might be able to be solved through configuring the source to send multi-line logs to Nagios Log Server, making it so that you can have all of the context within a single log. There are several resources on how to set up multi-line logging with different sources. Without knowing your source, here are documents for doing this with syslog and nxlog:
https://support.nagios.com/kb/article/n ... g-727.html
https://support.nagios.com/kb/article/h ... r-985.html

If your use case isn't something that looks like it can be resolved through multi-line logging, right now the manual filtering is the best way to go about it.

You can include context lines around log matches using a few approaches depending on your tool:
Using grep on Linux:
grep -C 3 "search_term" logfile.log
-C 3 shows 3 lines before and after each match. You can also use -B (before) or -A (after) for more precise control.
In NXLog or similar log collectors:
You can configure a Processor to buffer lines and output them when a match occurs, effectively giving you surrounding context.
In log analysis platforms (Elasticsearch, Kibana, Splunk):
Most have a “context” or “surrounding events” feature when viewing search results, letting you automatically pull a configurable number of entries before and after each match.
Using these methods saves time and gives a clearer picture of what’s happening around your search hits.

Exactly — context lines are crucial. A single match doesn’t always tell the story. Having before/after logs saves time and prevents misinterpretation.
Slope Rider