Feature Request: Enhanced 'Reactor System' Environment State
-
I miss the days of Vax mainframes, when I could sit at the terminal and pull all manner of Unix system variables seemingly out of thin air, which were great for tracking cron jobs and batch files.
Could the (already existing)
reactor_system
entity gain a few extra datapoints, such as (in descending order of importance):
◘ .last_rule_triggered.name // friendly rule name (string)
◘ .last_rule_triggered.id // rule _ID (string)
◘ .rules_set_by_name // array of currently SET reactions (rule names)
◘ .rules_set_by_id // array of currently SET reactions (rule _IDs)
◘ .rules_reset_by_name // array of currently RESET reactions (rule names)
◘ .rules_reset_by_id // array of currently RESET reactions (rule _IDs)Of course, not if any of this causes undue overhead in MSR! I realize much of this information can already be retrieved from Logs, but I'm looking toward including some of this "snapshot" information within SMTP messages sent to me whenever critical events happen, such as Vera restarting or rebooting without warning.
-
T toggledbits locked this topic on