Include more context in Event Rules

[llamafilm]

NetBox version

v3.7.0

Feature type

Change to existing functionality

Proposed functionality

When triggering a Python script using Event Rule, I'd like to have access to more context, just like Webhooks have. Currently the script only gets the data object. Webhooks also have:

• event
• username
• model
• snapshots

Use case

I want to log the username to have an audit trail. I also want to log whether the script was run manually or by an event rule.
I want to use the snapshot data to build more complex conditions into the script. For example, the event rule triggers on every device update, and the script updates my monitoring system. But I only want it to run if certain key fields were changed, like the name or status. Because other fields like airflow are irrelevant for monitoring.

Database changes

No response

External dependencies

No response

[renatoalmeidaoliveira]

I think its related to #14884

[llamafilm]

Yep, essentially the same request. Since you beat me to it, do you want to incorporate details from this request into yours and then close this one?

[jeremystretch]

This needs to remain a separate FR. #14884 specifically addresses passing an event rule's action data to a script, whereas this FR deals more generally with context.

I'm going to mark this as blocked by #14884; once that has been resolved we can look at opening it up to include additional context.

[SaschaSchwarzK]

It would be cool is the pre/post change data would be available in the conditions. Or a diff object that contains the changes. I currently face a problem that I get thousands of jobs as the condition in the event rules cannot look it down to a specific field that changed the value. So every time the item is changed, no matter what changed, the script is run.