Getting Data In

How to ingest multiple line JSON

JayKay1980
New Member

I have a JSON file that is formatted like this

 

{
    "meta": {
        "serverTime": 1692112678688.699,
        "agentsReady": true,
        "status": "success",
        "token": "ABCDEFG",
        "user": {
            "userName": "username",
            "role": "ADMIN"
        }
    },
    "vulnerabilities": [
        {
            "id": "pcysys_linux_0.10000000",
            "creation_time": 1690581702599.0,
            "name": "name",
            "summary": "summary",
            "found_on": "Host: 10.10.10.10",
            "target": "Host",
            "target_id": "abcdefg",
            "port": 445,
            "protocol": "abc",
            "severity": 3.5,
            "priority": null,
            "insight": "this is the insight",
            "remediation": "this is the remediation"
        },
        {
            "id": "pcysys_linux_0.10000000",
            "creation_time": 1690581702599.0,
            "name": "name",
            "summary": "summary",
            "found_on": "Host: 10.10.10.10",
            "target": "Host",
            "target_id": "abcdefg",
            "port": 445,
            "protocol": "abc",
            "severity": 3.5,
            "priority": null,
            "insight": "this is the insight",
            "remediation": "this is the remediation"
        }
    ]
}

 

I am trying to ingest just the vulnerabilities. It works when I try it in Splunk UI but when I save it in my props.conf file it doesn't split it correctly and the id from one section gets appended to the end of the previous one.

 

Here is what I am trying.

[sourcetype]
LINE_BREAKER = }(,[\r\n]+)
SHOULD_LINEMERGE = false
NO_BINARY_CHECK = 1

Labels (2)
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!

Vibe-coding, AI, and Splunkcraft: Highlights from the .conf26 Builder Bar

If you stopped by the Builder Bar at .conf26, thank you! This year, we brought ...

Thanks for the Memories: .conf26 Took Learning to New Heights

Thank you, Splunk Community, for making .conf26 in Denver one for the books. From packed Splunk University ...

Best Practices: Splunk auto adjust pipeline queue

When you enable autoAdjustQueue in Splunk, maxSize should be understood as the queue size Splunk starts with ...