phosphor-dbus-monitor/src/example, branch master

Modify parser and add mako scripts for watch on object path

2018-06-05T02:10:49+00:00

Added support for watch and callback on 'interface added' signal for the specified object paths. Added mako scripts for events to auto create callback and watch objects for the specified object path groups. Clients specify object paths to watch and callbacks to invoke in the config.yaml file Change-Id: I3fa2ea1520649120b927c0cb83a16e5cace2f24e Signed-off-by: Marri Devender Rao

Add ElogWithMetaDataCapture class

2018-02-27T18:36:05+00:00

This callback class will create an error log with exactly 1 metadata field, which takes a string. This metadata field will be filled in with the property paths, names, and values of the properties that passed the condition checks that caused the callback to be called in the first place. Tested: Ran with YAML rules that used this callback and checked that everything worked as specified. Change-Id: Ib37206c63385939c583a09e7ba979d6e016691f6 Signed-off-by: Matt Spinler

Add oneshot support to count conditions

2018-02-23T19:51:02+00:00

When a count condition is a oneshot, it will only trigger the callback the first time the condition is true. The condition needs to evaluate to false at least once to rearm the callback. A use case for this would be when a group of properties is being watched for a subset of them hit a certain value. Even though every properties changed signal for every property in the group would check the condition, only the first time the condition is true would the callback be issued. This behavior is specified with a 'oneshot: true' entry in the YAML. If not present, it defaults to false which is the original behavior. Tested: Verify this does indeed do what is advertised by modifying condition rules to consistently pass and checking behavior. Change-Id: Ie185621e86c605234bf329a5f38317267dbb6fb6 Signed-off-by: Matt Spinler

Adding the section for event call back.

2018-02-20T04:00:04+00:00

eg:- - name: example event callback description: > 'Callbacks are actions PDM should take when instructed to do so. Some callback types refer to a group of paths and group of properties in a similar fashion as the property watch directive. The event callback creates the event D-Bus object with the given name and the event message. eg /xyz/openbmc_project/events/test/' class: callback callback: event paths: example path group properties: example property group eventName: test eventMessage: "Test configuration changed." When fully implemented, event callbacks will create DBus objects for preconfigured DBus events. Change-Id: I73d46a9bc630763cc1a74877803a638f3a8d1e1f Signed-off-by: Ratan Gupta

Add resolve callouts test to YAML

2017-11-14T17:14:53+00:00

Change-Id: I9f21e6378f74bf9dd7d413557a80b47ec9c9f829 Signed-off-by: Matt Spinler

Add resolve callout example

2017-11-14T17:14:53+00:00

Change-Id: Ie80bff38947a79cc686eaf9db9c80453d28a4fb6 Signed-off-by: Matt Spinler

Add more elog tests

2017-08-21T14:26:46+00:00

Add tests to callbackgroupgentest/test.yaml Change-Id: I0b9d4799dd3ed3a4876115594aacbd80caa3f9d0 Signed-off-by: Gunnar Mills

Add elog to example.yaml

2017-08-21T14:26:43+00:00

Change-Id: I97f73dd310cae4b2d67122bc51414e2a5397f0b3 Signed-off-by: Gunnar Mills

Add tests for elog

2017-08-21T14:26:40+00:00

Change-Id: I58a6ac714cfa80462ab53d4487dc727e40038b06 Signed-off-by: Gunnar Mills

Grammar fixes in example.yaml

2017-08-14T19:03:14+00:00

Change-Id: Ia9ae40f1bd590945e2fee662e4437b92c8bd9b09 Signed-off-by: Gunnar Mills