Metrics provides system/device level helper methods. It is exposed as a singleton global namespace.
Metrics is the main entry point for this object family. Use it to understand the responsibility of the namespace before diving into the methods below it. Metrics provides system/device level helper methods. It is exposed as a singleton global namespace.
In system flow, design steps as observe first and act second when the API can affect device state. This API becomes most valuable in multi-step chained scenarios.
This entry does not require mandatory parameters. This entry is a namespace or helper object overview; the real flow is built with the methods listed below it.
Using this API with logging, error handling, and next-step control produces much more professional results than calling it in isolation.
The snippet below is a starter pattern that can be applied directly in runtime flow.
-- Metrics:enable
local result = Metrics:enable("value")
-- Use the result in your script flowFrom foundation to combined usage, each level is provided as a separate code block so you can copy the level you need and adapt it directly.
-- Metrics:enable
local result = Metrics:enable("value")
-- Use the result in your script flow-- Metrics:enable
local result = Metrics:enable("value")
-- Use the result in your script flow
-- Continue with one focused method on the object.-- Metrics:enable
local result = Metrics:enable("value")
-- Use the result in your script flow
local note = "Metrics overview loaded"
print(note)-- In system flow, design steps as observe first and act second when the API can affect device state.
local function run_metrics_step()
-- Metrics:enable
local result = Metrics:enable("value")
-- Use the result in your script flow
end
local ok, err = pcall(run_metrics_step)
if not ok then
toast("Step failed")
print(err)
end-- Metrics:enable
local result = Metrics:enable("value")
-- Use the result in your script flow
wait(200)
print("Combined with logging and flow control")