Lines Matching refs:trigger
26 with metrics report and trigger management. This service is described later in
314 The trigger management D-Bus object:
323 to create new trigger for the certain metric. The method's parameters allow to
324 define the type of metric for which trigger is set (discrete or numeric). Depend
325 on this setting, this method accepts different set of trigger parameters.
327 For discrete metric type, trigger parameters contain:
331 … | Discrete trigger condition: <br> "Changed" - trigger occurs when value of metric has c…
332 | DiscreteTriggers | array of structures | Array of discrete trigger structures. …
338 | TriggerId | string | Unique trigger Id …
340 | Value | variant | Value of discrete metric, that constitutes a trigger event. …
341 … | uint64 | Time in milliseconds that a trigger occurrence persists before the action defined for…
343 For numeric metric type, trigger parameters contain numeric thresholds. Numeric
350 | ThresholdType | enum | Numeric trigger type: <br> "UpperCritical" - reading is above normal r…
351 … | uint64 | Time in milliseconds that a trigger occurrence persists before the action defined for…
352 …trigger the threshold's action:<br> "Increasing" - trigger action when reading is changing from be…
353 | ThresholdValue | variant | Value of reading that will trigger the threshold …
355 The `AddTrigger` method also allows to define the specific action when trigger
356 is activated. Upon the trigger activation, three possible actions are allowed,
360 In order to assign trigger to specific metric, the metric parameter is defined.
365 | SensorPath | object path | D-Bus path to sensor, for which trigger is defined. …
367 …t which update shall be triggered when trigger condition occurs. This is optional and shall be fil…
369 The `AddTrigger` method also allows to set trigger's persistency (whether
370 trigger shall be stored in the BMC's non-volatile memory).
375 String for created trigger - ie. '/xyz/openbmc_project/Telemetry/Triggers/{Domain}/{Name}'
378 Such created trigger implements the `xyz.openbmc_project.Object.Delete` and the
379 `xyz.openbmc_project.Telemetry.Trigger` interfaces. Each trigger object contains
381 numeric). This information determines which triggers are stored within trigger
384 If trigger is defined for discrete metric type, than it contains trigger
389 … | Discrete trigger condition: <br> "Changed" - trigger occurs when value of metric has …
390 | array of structures | Array of discrete trigger structures. …
392 Discrete trigger structure:
396 | string | Unique trigger Id …
398 | variant | Value of discrete metric, that constitutes a trigger event. …
399 | uint64 | Time in milliseconds that a trigger occurrence persists before the action defined in th…
401 If trigger is defined for numeric metric type, than it contains information
406 | enum | Numeric trigger type: <br> "UpperWarning"<br>"UpperWarning"<br>"LowerCritical"<br>"Lowe…
407 | uint64 | Time in milliseconds that a trigger occurrence persists before the action defined in th…
408 | enum | Indicates direction of crossing the threshold value that trigger the threshold's action…
409 | variant | Value of reading that will trigger the threshold …
411 The trigger object also contains information about reading, for which trigger
416 | object path | D-Bus path of sensor. This is a path to the sensor, for which reading trigger is de…
418 | object path | D-Bus path of existing reading report. This is required when trigger's action is to…
461 3. For action Update, the Telemetry service will trigger the update of reading
462 report pointed by it's D-Bus path contained in trigger object properties. The
522 | whether trigger value is exceeded |
629 Sample trigger, that will trigger metric report update: