Splunk Search

Sendmail transactions

htaylor
New Member

When searching for email addresses in our sendmail logs, it helps to see the full transaction by using the queue id (qid) field.

Search command:

sourcetype="sendmail_syslog" | transaction fields=qid maxspan=1m maxpause=30s | search [email protected]

Example output:

Apr 16 12:35:55 server1 sendmail[13643]: o3GHZsNn013643: from=<[email protected]>, size=1126, class=0, nrcpts=1, msgid=<[email protected]>, proto=ESMTP, daemon=MTA, relay=mail.example.com [192.168.1.1]
Apr 16 12:35:56 server1 sendmail[13656]: o3GHZsNn013643: to=<[email protected]>, delay=00:00:01, xdelay=00:00:00, mailer=smtp, pri=121126, relay=mail.example.com [192.168.1.1], dsn=2.0.0, stat=Sent (Ok: queued as 2DA7D50210)

Fields:

host=server1 | sourcetype=sendmail_syslog | source=/var/log/maillog | to=<[email protected]> | from=<[email protected]> | relay=[192.168.1.1] | relay=mail.example.com | size=1126 | delay=00:00:01 | process=sendmail | qid=o3GHZsNn013643


Currently transactions take a long time to process, especially if I am looking at an entire days worth of email records to search for one email address. Can someone show me which search options would allow me to search for the email address first then pass the qid results list to a new search and run a transaction against that. sourcetype="sendmail_syslog" [email protected] | fields qid …?

I have looked at this question already: "http://answers.splunk.com/questions/284/subsearch-like-correlated-subquery-in-sql", but it still does not provide a clear answer. Do I use a subsearch or use the map command and how would I use it in this example?

Tags (2)
0 Karma
1 Solution

gkanapathy
Splunk Employee
Splunk Employee
sourcetype=sendmail_syslog [ search sourcetype="sendmail_syslog" [email protected] | dedup qid | fields qid ] | transaction fields=qid maxspan=1m maxpause=30s

should do it better

View solution in original post

carasso
Splunk Employee
Splunk Employee

The searchtxn was created for this exact use case. It also does the transitive closure when you have multiple fields involved and not just one. To do that yourself you'd need to have a subsearch of a subsearch, etc.

| searchtxn email to=[email protected]

0 Karma

gkanapathy
Splunk Employee
Splunk Employee
sourcetype=sendmail_syslog [ search sourcetype="sendmail_syslog" [email protected] | dedup qid | fields qid ] | transaction fields=qid maxspan=1m maxpause=30s

should do it better

htaylor
New Member

This works great. Thanks.

0 Karma
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...

Skip the Awkward Silence: Have a .conf-ersation at .conf26

Picture this. You arrive at .conf26 already having your socializing and networking plans mapped out. No ...

Rethinking Zero Trust: From Product Purchases to Logical Control Evidence

Implementing Zero Trust (ZT) across complex environments often falters at the very beginning due to a ...