# TimeLine as Weblogic Flow Trace

**URL:** <https://discuss.elastic.co/t/timeline-as-weblogic-flow-trace/277322>\
**Category:** APM\
**Tags:** java\
**Created:** [June 29, 2021, 8:36am UTC](https://discuss.elastic.co/t/timeline-as-weblogic-flow-trace/277322 "2021-06-29T08:36:03Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![TidalPoo](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tidalpoo/32/90955_2.png) [@TidalPoo](https://discuss.elastic.co/u/TidalPoo)\
**Post date:** [June 29, 2021, 8:36am UTC](https://discuss.elastic.co/t/timeline-as-weblogic-flow-trace/277322/1 "2021-06-29T08:36:04Z")

</div>

Hi all!

I'am trying create APM monitoring on weblogic soa server.

It's working ok, agent is connecting, information retrieve, but that's not what i want.

Weblobgic EM has a function, Flow instance -\> Flow trace

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/a/9/a9a9af911450fd051296eada1e81d3cfaa494903.png)

can I do something like this in APM?

---

<div class="post-metadata">

**Author:** ![Sylvain\_Juge](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sylvain_juge/32/55521_2.png) [@Sylvain\_Juge](https://discuss.elastic.co/u/Sylvain_Juge)\
**Post date:** [July 5, 2021, 9:43am UTC](https://discuss.elastic.co/t/timeline-as-weblogic-flow-trace/277322/2 "2021-07-05T09:43:24Z")

</div>

Hi @TidalPoo ,

I'm not familiar with Weblogic EM/SOA, but it looks like Flow Trace here is very specific to Weblogic. Does it behaves more like a message-driven framework (like Kafka/JMS), or more like a request/response lifecycle where each would be instrumented as a transaction ?

We don't have automatic support for this, but you could still use APM agent + our [Public API](https://www.elastic.co/guide/en/apm/agent/java/current/public-api.html) to create transactions programatically by using any hooks that Weblogic could provide (if there is something similar to `Filter` in `Servlet` API, that's a good candidate).

---

<div class="post-metadata">

**Author:** ![TidalPoo](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tidalpoo/32/90955_2.png) [@TidalPoo](https://discuss.elastic.co/u/TidalPoo)\
**Post date:** [July 7, 2021, 12:52pm UTC](https://discuss.elastic.co/t/timeline-as-weblogic-flow-trace/277322/3 "2021-07-07T12:52:18Z")

</div>

HI @Sylvain_Juge  
thank you for your answer

How can I configure the agent to commit a transaction based on a specific ID in the metadata? Any doc? weblogic has a flow ID, and I want to make a timelilne based on this ID, and not by classes and methods

---

<div class="post-metadata">

**Author:** ![Sylvain\_Juge](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sylvain_juge/32/55521_2.png) [@Sylvain\_Juge](https://discuss.elastic.co/u/Sylvain_Juge)\
**Post date:** [July 8, 2021, 7:18am UTC](https://discuss.elastic.co/t/timeline-as-weblogic-flow-trace/277322/4 "2021-07-08T07:18:16Z")

</div>

Unfortunately, this is not possible, but what you can do is to capture the Flow ID with a label [Public API | APM Java Agent Reference [1.x] | Elastic](https://www.elastic.co/guide/en/apm/agent/java/current/public-api.html#api-transaction-add-tag)

So, while the trace itself will remain "as it was executed and captured by the agent", you can build correlation between the Flow ID and the Transaction/Span ID.

Also, if using [log correlation](https://www.elastic.co/guide/en/apm/agent/java/current/log-correlation.html) feature, you can inject the Trace ID into the application logs. I need to check if we can also use tags here to allow injecting both Transaction ID and the Flow ID directly into logs.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [July 29, 2021, 3:18am UTC](https://discuss.elastic.co/t/timeline-as-weblogic-flow-trace/277322/5 "2021-07-29T03:18:47Z")

</div>

This topic was automatically closed 20 days after the last reply. New replies are no longer allowed.
