...
Placeholder | Description |
$now | extractor current execution time in system time zone |
$today | extractor current execution date in system time zone |
$yesterday | extractor day before execution date in system time zone |
$timestamp | extractor current timestamp in UTC |
$lastrunts | extractor last execution timestamp in UTC (this is obsolete but still supported, it is recommended to use $lastrun) |
$lastrun | extractor last execution timestamp in UTC |
$lastrundate | extractor last execution date (system time zone) |
$lastruntime | extractor last execution time (system time zone) |
$lastrun_st | extractor last execution timestamp in system time zone |
$timestamp_st | extractor current timestamp in system time zone |
In version 8.01, an enhanced functionality has been introduced to facilitate a more dynamic testing experience when using placeholders within conditions. This enhancement provides users with a popup screen where placeholder values can be adjusted, offering greater flexibility and ease of testing.
Example Scenario: Consider the scenario where the placeholder $yesterday is utilized in a script, and the calculated value for $yesterday is 24.03.2024. In situations where there is no data available for this specific date, the enhanced functionality in version 8.01 allows for the modification of this placeholder value for testing purposes.
This means that users now have the option to change the value assigned to $yesterday directly from the popup screen. By doing so, testing scenarios can be more accurately simulated, ensuring the script behaves as expected under various conditions.
This enhancement streamlines the testing process, enabling users to validate script behavior with different placeholder values without the need for manual adjustments within the script code.
Splunk Event
Important: The fields will vary significantly based on the SQL script selection criteria specified in the Metric Filter
...