Scheduler Global Variables

Knowledge Base
1

Scheduler Global Variables

AMP 2.5 has a number of global variables available to scheduled tasks in addition to the ones exposed by the trigger. They use the exact same {@Key} syntax, but substitute different values. For example, {@CPUUsage} will substitute for the current instances CPU usage.

Key Description
InstanceName Name of the current instance
InstanceId ID of the current instance
Uptime Uptime of the current instance
State State ID of the current instance
StartTime Time the application was started within the instance (if running)
ApplicationName Name of the application as exposed by its configuration
RAMUsage RAM usage in megabytes
CPUUsage CPU usage as a percentage (without %)
MaxUsers User limit of the application (if applicable)
UserCount Number of connected users (if applicable/available)
TriggerId The ID of the scheduler trigger that fired the event
TriggerName The Name of the scheduler trigger that fired the event
1 Like
2

What unit is Uptime - seconds? minutes? days? milliseconds?

4

Having variables is great, but what type of values should we expect as a return for each, and, for example, {@State} returns an ID, what these IDs actually mean? Where can I find the possible returns for these variables?

5

Is there any plan to extend this with useful functions like: time, date, timestamp, simple mathematic functions like {current players-1} etc?

1 Like