Map dotted attribute names literally in a pipeline log exporter

Source facts

The pipeline troubleshooting guide says recordMap does not support multilevel dot notation such as attributes.foo.bar; it directs users to bracket notation, attributes[‘foo.bar’], instead. The map must also supply TimeGenerated, and its target column names must match the destination schema. These requirements concern the exporter mapping, not just whether telemetry reached the receiver. Microsoft Learn.

Applicability

Inspect the actual incoming attribute names and the exporter’s api.schema.recordMap. This brief concerns a literal dotted key in that mapping; it does not define general JSON traversal or promise that every nested source structure has the same representation. Identify the intended destination columns before modifying the expression.

DSE recommendation

Compare the literal incoming attribute keys with recordMap expressions before changing the destination table or transport. Retain a redacted representative record beside the proposed mapping. Have the schema owner distinguish a period that belongs to the key from a presumed level in a hierarchy. Review the timestamp mapping and destination spelling in the same small change.

Verification

Send a harmless record with a known dotted attribute value and a known timestamp. Check the stored destination values rather than relying only on an accepted configuration or network connection. Include a record without that attribute to observe the approved handling of absence. Preserve the input, mapping, resulting columns, and any exporter error, and resolve mismatches before expanding the change to other dataflows.

Official references

Microsoft Learn: Troubleshoot Azure Monitor pipeline. Source reviewed September 9, 2026.