Getting Data In

JSON : why was the field "tag" not extracted?

LordSnooz
Explorer

Hi,

I have logs from Docker in JSON format posted to Splunk HTTP Event Collector. All fields are dynamically recognized, but the last field tag is never recognized. Is it possible that this is due to the duplicate source field just before field tag? The source field seems to be a default Splunk field and it’s extracted twice : in the raw and in the input source.

Here's some examples of some JSON events:

{"line":{"time":"2018-09-05 15:39:27.370","level":"silly","message":"Healthcheck:Completed"},"source":"stdout","tag":"dc7eb5ace680","attrs":{"appName":"ms-chatservice","appType":"microservice"}}

{"line":{"time":"2018-09-05 15:56:27.267","level":"debug","message":"KafkaBase.getTopicMetadata: Test"},"source":"stdout","tag":"6960306e978c","attrs":{"appName":"ms-chatservice","appType":"microservice"}}

{"line":"\u001b[0mGET /api/protected/notifications?skip=0\u0026limit=100 \u001b[36m304 \u001b[0m56.743 ms - -\u001b[0m","source":"stdout","tag":"1b6e7b4e756e","attrs":{"appName":"web-pro","appType":"webapp"}}

Does someone have an idea why?

Regards,

Tags (2)

davebo1896
Communicator

perhaps because "tag" is a reserved field in Splunk?

0 Karma
Get Updates on the Splunk Community!

Upcoming Webinar: Unmasking Insider Threats with Slunk Enterprise Security’s UEBA

Join us on Wed, Dec 10. at 10AM PST / 1PM EST for a live webinar and demo with Splunk experts! Discover how ...

.conf25 technical session recap of Observability for Gen AI: Monitoring LLM ...

If you’re unfamiliar, .conf is Splunk’s premier event where the Splunk community, customers, partners, and ...

A Season of Skills: New Splunk Courses to Light Up Your Learning Journey

There’s something special about this time of year—maybe it’s the glow of the holidays, maybe it’s the ...