1. Docs
2. Send Data to Honeycomb
3. Honeycomb Telemetry Pipeline
4. Honeycomb Telemetry Pipeline Processors
5. Parse XML

Parse XML

Table of Contents

Description 

The Parse XML Processor is utilized to parse XML document strings from specified fields within log, metric, or trace data. It’s particularly useful when your telemetry data contains a serialized XML document, and you need to convert them into a structured format for easier analysis and filtering. The processor supports specifying the source field and the target field for the parsed XML data, offering flexibility in handling diverse data structures.

Use 

When dealing with telemetry data that includes an XML document embedded within logs, metrics, or traces, the Parse XML Processor becomes instrumental. For instance, logs from certain applications or systems might contain XML documents representing specific attributes or metadata. By utilizing the Parse XML Processor, these XML documents can be parsed and converted into structured data, enhancing readability and facilitating more complex queries and analyses.

The parsed XML is structured as follows:

1. All character data for an XML element is trimmed and placed in the content field.
2. The tag for an XML element is trimmed and placed in a tag field.
3. The attributes for an XML element is placed as a mapping of attribute name to attribute value in the attribute field.
4. Processing instructions, directives, and comments are ignored and not represented in the parsed XML.
5. All child XML elements are parsed as above, and placed in an array in a children field.

As an example, see the following XML:

<?xml version="1.0" encoding="UTF-8" ?>
<Log>
  <User>
    <ID>00001</ID>
    <Name type="first">Joe</Name>
    <Email>joe.smith@example.com</Email>
  </User>
  <Text>User fired alert A</Text>
</Log>

This XML, when parsed, becomes:

{
  "tag": "Log",
  "children": [
    {
      "tag": "User",
      "children": [
        {
          "tag": "ID",
          "content": "00001"
        },
        {
          "tag": "Name",
          "content": "Joe",
          "attributes": {
            "type": "first"
          }
        },
        {
          "tag": "Email",
          "content": "joe.smith@example.com"
        }
      ]
    },
    {
      "tag": "Text",
      "content": "User fired alert A"
    }
  ]
}

Configuration 

Example Configurations 

Parse XML from Logs 

In this example, we have a basic log that details an action and the user that triggered the action, like an audit log. This log is in XML format, and we’d like to parse the content into a structured log.

Here is a sample log record:

{
  "body": "<Log><User><ID>00001</ID><Name><First>Joe</First></Name></User><Text>User did a thing</Text></Log>"
}

In order to parse the body of the log record, and store it on the parsed_xml attribute, we can configure the Parse XML processor as follows:

• Telemetry: Logs
• Condition: true
• Source Field Type: Body
• Source Field: Left empty
• Target Field Type: Attribute
• Target Field: parsed_xml

After parsing, the log record looks like this:

{
  "body": "<Log><User><ID>00001</ID><Name><First>Joe</First></Name></User><Text>User did a thing</Text></Log>",
  "attributes": {
    "parsed_xml": {
      "children": [
        {
          "children": [
            {
              "content": "00001",
              "tag": "ID"
            },
            {
              "children": [
                {
                  "content": "Joe",
                  "tag": "First"
                }
              ],
              "tag": "Name"
            }
          ],
          "tag": "User"
        },
        {
          "content": "User did a thing",
          "tag": "Text"
        }
      ],
      "tag": "Log"
    }
  }
}

Did you find what you were looking for?

Yes No

---

If you have questions, join our Pollinators Community Slack!
Pro/Enterprise users can visit Honeycomb Support or email support@honeycomb.io.

Submit