Monitoring Splunk

Poor search performance one sourcetype

Path Finder

I have events that look like this:



crcSalt =

disabled = false

followTail = 0

sourcetype = nvdb




BREAK_ONLY_BEFORE = (?i)<entry\sid=

MUST_BREAK_AFTER = (?i)</entry>

MAX_EVENTS = 10000

REPORT-nvdb_vulnerable_products = nvdb_vulnerable_products

EXTRACT-cve_id = (?i)<entry\sid=\"CVE-(?P\d+-\d+)

EXTRACT-score = (?i)<cvss:score>(?P[^<]+)<

EXTRACT-access_vector = (?i)<cvss:access-vector>(?P[\w+]+)<

EXTRACT-access_complexity = (?i)<cvss:access-complexity>(?P[\w+]+)<

EXTRACT-authentication = (?i)<cvss:authentication>(?P[\w+]+)<

EXTRACT-confidentiality_impact = (?i)<cvss:confidentiality-impact>(?P[\w+]+)<

EXTRACT-integrity_impact = (?i)<cvss:integrity-impact>(?P[\w+]+)<

EXTRACT-availability_impact = (?i)<cvss:availability-impact>(?P[\w+]+)<

The data is XML formatted. The files are treated as a single event and are around 250 lines long. The searches hang at like 538 events (out of tens of thousands).

What's the best way to go about troubleshooting this? I have other XML inputs that take no time at all to search through.



Tags (1)
0 Karma

Path Finder

The problem was a transform that had to parse dozens or more lines out of each event. Disabling that transform caused the performance to return to normal.

0 Karma
Get Updates on the Splunk Community!

Introducing Ingest Actions: Filter, Mask, Route, Repeat

WATCH NOW Ingest Actions (IA) is the best new way to easily filter, mask and route your data in Splunk® ...

Splunk Forwarders and Forced Time Based Load Balancing

Splunk customers use universal forwarders to collect and send data to Splunk. A universal forwarder can send ...

NEW! Log Views in Splunk Observability Dashboards Gives Context From a Single Page

Today, Splunk Observability releases log views, a new feature for users to add their logs data from Splunk Log ...