As in title. I don't believe this is currently audited and we've just found a need for it
Uhm, no. If you are using trial mode, it's a trial. I would argue that this would pollute the audit of a trial.
Well, they have a licence but they split it up into frontend/backend years ago and moved the Alarm Notification module to the Backend, but never bothered to remove the Alarm Notification module from the Frontend despite it being unused, so the "reset trial" button is still there.
I don't see how this would pollute the audit log? It happens so infrequently that it's insignificant. (what pollutes the audit log is gateway scoped - not including Perspective - calls to system.tag.write* inserting entries into the audit log for things that you really don't want to include)
Also, I know you're going to say that the solution in this case is to simply remove the Alarm Notification module, which I agree with, but I still would like this audited
That last does not go with the other two. 
"this" in that case meant "trial reset pushed" being added into the audit log, if that wasn't clear
It was clear, and I strongly disagree that it belongs. Nothing related to trial mode belongs.
Does resetting the trial on an unused module have consequences on the system? Like, does it restart scripting or something along those lines?
No.
1 Like