IBM webMethods Hybrid Integration

Are you saving the pipeline or using logged fields. If you save the pipeline then it will store it as a blob. This is both costly and of no use to you, as you cannot use it for tracking. 
if you use logged fields then it will simply save a key value pair for each attribute you checked. Cost is minimal and you can use this table to the find the transactions that you want. 

also don’t forget the service setContextID, which also allows you to set an explicit business identifier for your transaction and all subsequent steps. 

You have kind of answered your own questions. Audit DB isn't ideally suited for a production setup where you want to track data from a high volume call. It has never performed really well for the reasons you mentioned. There are a couple of alternatives:

1. Write your own  service to write to a store of your choice. You can call the service asynchronously or, if you need throttling, you can publish a doc and then call the service from the trigger.

2. Modern systems do this using OpenTelemetry traces and metrics. So if you have an APM tool, then you can go that route. I have done that at some customers using our OpenTelemetry package called Otelscope. But that is only relevant if you have an APM tool or are planning to use one.

@Rupinder Singh is of course correct. If you

simply to be able to filter or perform some

light weight reporting, my solution will work. 
for large volumes or more complex tracking then better to use the proper tooling but of course that is a major investment and maybe beyond the he scope of your project. 

Thanks Guys - perfect answers :-) I don't need the pipeline so it sounds like auditing should be fine - thanks for your help !

HI Again- spoke to soon :-( I've stopped saving the pipeline which was where I was getting my audit data from - which table is the logged fields stored in?

thanks again !

You can see the logged field values in the WMSERVICECUSTOMFLDS table.

To get the service context, you can join that table to WMSERVICE using the CONTEXTID columns in each table. Note that WMSERVICE gets two rows per service invocation. You need to filter the STATUS column to narrow it down to just the service start or end rows.

Sorry about this - I've just rounding out on this...

is the package name in the db anywhere ? I've looked everywhere but can't see it. I get the impression that the wM gets it from the runtime context rather than the audit logs?

many thanks !

john.