Any way to extract BizEvent entry to a Log?

[siavash1996]

Hi there,

We use Business Events capture with OneAgent to ingest request body (payloads) for a subset of incoming requests to our application. Just as an example, we ingest ACS events, like users badging in and out of work sites, from our customers, and we can use BizEvents to capture that payload for future reference if there's some kind of error reported by the customer. This works great, as I'm able to run "fetch bizevents" in a Notebook and gather tons of info for any given payload, including things like k8s.pod.name, trace_id, span_id, and more.

However, despite all of that data being captured, Dynatrace doesn't show these BizEvent entries if I pull up that specific trace in the Distributed Tracing app. The BizEvent has all the necessary data that would need for it to be auto-correlated with the correct span and trace, but Distributed Tracing will not show any log entries that do not appear in "fetch logs".

To address this, I was hoping I could maybe utilize OpenPipeline to perform some processing, like a Data Extraction step, to convert the entry into a standard "log", but the Business Events OpenPipeline doesn't seem to offer that kind of processor. This adds an additional unnecessary hop into the Notebooks app to view captured BizEvents for any trace, when this data should really be auto-correlated to the trace considering it has every bit of necessary info.

Is this an intentional functionality gap for some reason? Are there any workarounds? Any plans to implement this sort of feature, either automatically or via OpenPipeline, in the future? Just seems like such an easy win that would be hugely beneficial to companies like ours.

[sujit_k_singh]

Hi @siavash1996 

You've identified a genuine functionality gap. Business Events (BizEvents) captured via OneAgent are stored in a separate data bucket (bizevents) and are not automatically correlated with distributed traces in the Distributed Tracing app even when they contain valid trace_id and span_id fields. The Distributed Tracing view only displays entries from fetch logs, not fetch bizevents. Get business events from logs and spans — Dynatrace Docs

As you noted, the Business Events OpenPipeline doesn't offer a processor to "convert" a BizEvent into a log entry. The OpenPipeline for Business Events supports enrichment, filtering, and routing  but not cross-table type conversion (BizEvent → Log). Interestingly, the reverse direction is supported: OpenPipeline can convert logs and spans into business events. But there's no equivalent "BizEvent → Log" pipeline processor.

This means that even though your BizEvents contain all the necessary correlation data (trace_id, span_id, k8s.pod.name), there's currently no native mechanism to surface them within the Distributed Tracing app alongside log entries.

Thanks,

Sujit