All Apps and Add-ons

XML Input / first character is missing

tcoq
Path Finder

Hi together,

I'am trying to get some XML input into Splunk, but everytime the first character ("<") is missing. Due to this, Splunk cannot read XML correctly: (on two different sources)

from example-source: www.ecb.europa.eu/stats/eurofxref/eurofxref-daily.xml

this input:
<xml version="1.0" encoding="UTF-8"?><gesmes:Envel...
is getting this:
xml version="1.0" encoding="UTF-8"?><gesmes:Envel...

Is there anyone who knows why the first character is missing?

Best regard
Steffen

Tags (1)
0 Karma

mtimmsj
Explorer

The display issue appears to be corrected in 6.0.1.

yannK
Splunk Employee
Splunk Employee

This is a display issue, when you display with
source=myxmlsource | table _raw, the "<" is present.

by the way the xml starts with <?xml not <xml

when I test with <xml version="1.0" encoding="UTF-8">, the event are correctly displayed.

mtimmsj
Explorer

Hmmm if I pipe my sources to spath and then pipe that to xmlkv, I get the results I expect.

0 Karma

tries
Path Finder

I'm having exactly the same issue. My props.conf:

[host::rabbitmq]

SHOULD_LINEMERGE = true

BREAK_ONLY_BEFORE = \<\?xml\sversion

Is there a solution available for this issue ?

Thanks,

Thorsten

0 Karma

mtimmsj
Explorer

How did your ticket go? Should I send my colleague - who has access support - to open a Splunk ticket as well?

0 Karma

tries
Path Finder

just checked this with Splunk 5.0.5 and it's working. Seems like an Splunk 6.0 bug. I'll open a Splunk ticket.

0 Karma
Get Updates on the Splunk Community!

Shape the Future of Splunk: Join the Product Research Lab!

Join the Splunk Product Research Lab and connect with us in the Slack channel #product-research-lab to get ...

Auto-Injector for Everything Else: Making OpenTelemetry Truly Universal

You might have seen Splunk’s recent announcement about donating the OpenTelemetry Injector to the ...

[Puzzles] Solve, Learn, Repeat: Character substitutions with Regular Expressions

This challenge was first posted on Slack #puzzles channelFor BORE at .conf23, we had a puzzle question which ...