All Apps and Add-ons

How to parse RESULTS field from Qualys TA

jamesco
Engager

The Qualys documentation for the TA states that there may be a problem with parsing the RESULTS field because some values are multi-line values. Since this is the only field that may contain a multi-line value, what would be the best way to parse the data?

From props.conf:

[qualys:hostDetection]
DATETIME_CONFIG = 
NO_BINARY_CHECK = true
SHOULD_LINEMERGE = true
category = Custom
disabled = false
KV_MODE = auto

KV_MODE = auto parses all the fields correctly, except when the RESULTS field has a multi-line value.

Thanks in advance!

0 Karma
1 Solution

jamesco
Engager

Adding BREAK_ONLY_BEFORE = (HOSTVULN:|HOSTSUMMARY:) to props.conf resolved my issue.

View solution in original post

jamesco
Engager

Adding BREAK_ONLY_BEFORE = (HOSTVULN:|HOSTSUMMARY:) to props.conf resolved my issue.

jack19
New Member

Hi @jamesco ,

Hope you are doing well!

We are also trying to parse RESULTS field from Qualys TA, but event parsing having issue. I have updated props.conf as above. Could please help me on this? Did you updated any python script to parse events properly.

Thanks in advance.

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!

Index This | What travels the world but is also stuck in place?

April 2026 Edition  Hayyy Splunk Education Enthusiasts and the Eternally Curious!   We’re back with this ...

Discover New Use Cases: Unlock Greater Value from Your Existing Splunk Data

Realizing the full potential of your Splunk investment requires more than just understanding current usage; it ...

Continue Your Journey: Join Session 2 of the Data Management and Federation Bootcamp ...

As data volumes continue to grow and environments become more distributed, managing and optimizing data ...