Find out who did a cockpit DMN change/deployment

We use a DMN table to configure a threshhold/percentage. Now the value has been changed in the cockpit and we wonder: Who Did it?
I don’t see any user ids in the DB columns nor any information in cockpit oplog, deployment history, …

Can we find out who did changes/played with fire?

Thanks
Jan

I don’t know how and whether it’s possible to find out this. Audit logging is not the strongest side of the cockpit.

Wouldn’t it be a solution for you to disable DMN editing altogether? I.e. that a change can only be made via deployment?

Hi @jangalinski

Deploying a DMN file should result in an entry being added to the user operation log including the user ID of the user who performed the deployment. I believe the same behavior should apply to live editing as it ultimately creates a deployment. Personally, I haven’t tested the live editing feature since I have only worked with the community edition of Camunda 7.

That’s not an option, we explicitly use DMN in this case to allow live editing of threshhold values without restart/redployment of the app …

Our workaround for now: After live editing, we can give a name for the resulting single file deployment. We use this name to indicate the user id.

I will explore the operation log idea, though, thanks!

Could you shed some light on how you do it? Or is this just your thoughts on how to do it (but you haven’t implemented it yet)?

I just name the deployment. After you change the DMN and confirm the “play with fire” warning, you get a dialog where you can name the deplyoment. It defaults to something like “SpringBootAutoDeployment”, but it is changable. So I use this text field to annotate “Jan G - setting price threshhold to 100”. This is not perfect, but in the “deployments” overview I now see one deployment with the name I gave, containing the one DMN I changed.

1 Like

Thank you for the insight. But this is based on the fat that you’re a good citizen (like non-preemtive threading). If I edit the table (set the price threshold to 1000000) and name the deployment “Jan G setting to 1000000”… Ahem…

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