11 Dec 2025 09:14 AM - edited 11 Dec 2025 09:14 AM
Hi,
I'm in the process of migrating all logs configurations from the classic settings to OpenPipeline, and I noticed that the one thing that seems to be missing in OpenPieline is "Log Events".
As far as I understand, the moment I'll route all my logs from the classic pipeline to a custom route, log events settings won't apply anymore.
Is that true? How can create the same effect as Log Events in OpenPieline?
Thanks.
Solved! Go to Solution.
11 Dec 2025 09:47 AM
To achieve log event extraction in OpenPipeline, you should use Davis event extraction. This feature allows you to define rules in OpenPipeline that detect specific log patterns and generate events, similar to the classic "Log Events" functionality. Set up Davis event extraction rules in your OpenPipeline configuration to ensure that important log entries are turned into Davis events, even after migrating away from the classic pipeline.
11 Dec 2025 09:55 AM
I now realize that I couldn't find this setting since you must first click on "Migrate to new API of OpenPipline" to use it.
Thanks Thomas.
11 Dec 2025 09:58 AM
Before the migration the Davis extraction is there as well, but it's not its own stage. It's part of "Data extraction".
24 Aug 2026 03:00 PM
Hi Thomas,
I know that I'm replying to a older thread but I'm just having a look at this approach myself and working through the docs and found this post so thought I'd keep them together.
If we were wanting to generate an info only event for an entity and not generate a problem records (i.e. a user action) - can that be done through the Pipeline? The documents only quote a davis-event which in turn triggers a problem to be created.
Thanks
25 Aug 2026 07:55 AM
depending on what you want to achieve you can also use generic events or there are also info-level davis events.
Featured Posts