Getting Data In

Cisco ESA Textmail Summary Index

david_monaghan
Engager

Hi All,

I am trying to create summary index for Cisco ESA Textmail logs. I will then rebuild the Email data model using the summary index.

The scheduled search is running correctly but when I try to search the summary index I get no events returned.

How does one check that events are going into the summary index correctly?

Steps Taken

  1. Created a new index called email_summary
  2. I have created a scheduled search to run every 15 minutes
  3. In the settings I have ticked 'Enable summary indexing'

Saved Search

 

index=email sourcetype=cisco:esa:textmail 
| stats values(action) as action, values(dest) as dest, values(duration) as duration, values(file_name) as file_name, values(message_id) as message_id, values(recipient) as recipient, dc(recipient) as recipient_count, values(recipient_domain) as recipient_domain, values(src) as src, values(src_user) as src_user, values(src_user_domain) as src_user_domain, values(message_subject) as subject, values(tag) as tag, values(url) as url, values(user) AS user values(vendor_product) as vendor_product, values(vendor_action) as filter_action, values(reputation_score) as filter_score BY internal_message_id

 

 

Thanks,

Dave

0 Karma
1 Solution
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!

From Data to Insight: Announcing the Winners of the Splunk Dashboard Contest

Hi Splunkers, First off, thank you to everyone who participated in our very first From Data to Insight: The ...

Splunk Developers: Construct Your Future at the .conf26 Builder Bar

Calling all Splunk architects, platform admins, and app developers: the site is open, and the blueprints are ...

Quick connection discovery mode for forwarders

When a Splunk forwarder loses connectivity to its indexers, it does not always reconnect immediately. In many ...