"A developer can add a new attribute to a log or span and see it appear in their observability backend without updating a central schema definition. For fast-moving teams, this is convenient. However, as systems grow, the lack of structure begins to create friction."
"A field representing a user identifier might be named user_id in one service, uid in another, and customerId in a third. Status codes might be logged as integers in some contexts and strings in others. Optional attributes may be present only in certain deployments."
"Dynamic mapping systems do not prevent this. They accept new fields and attempt to reconcile type differences where possible. When reconciliation fails, the result may be index conflicts or dropped fields. When reconciliation succeeds, it can mask underlying inconsistency."
"As developers add attributes for debugging or experimentation, those attributes are often left in place. Over time, the number of distinct fields across logs and spans increases significantly. This can affect storage efficiency, index performance, and query planning."
Modern systems generate massive telemetry volumes through logs, metrics, traces, and events. Observability platforms use flexible, schema-on-read approaches enabling automatic field indexing without central coordination. While this lowers entry barriers for developers adding new attributes, it creates problems at scale. Multiple teams instrumenting services independently introduce inconsistencies—identical concepts named differently across services, type mismatches, and optional fields appearing sporadically. Dynamic mapping systems accept these variations but cannot prevent underlying inconsistency, sometimes masking problems through type reconciliation. Additionally, developers frequently leave experimental attributes in place, causing field proliferation that degrades storage efficiency, index performance, and data model clarity.
Read at DevOps.com
Unable to calculate read time
Collection
[
|
...
]