using phosphor-dbus-monitor

[Wim Vervoorn]

Hello Matt,

I stripped one down to what I think is the bare minimum and included it in this email. I guess once I have this working the others should be fine as well.

Basically this yaml doesn't make much sense but I expected this to generate journal entries.

- name: voltage sensor path group
  class: group
  group: path
  members:
    - meta: SENSOR
      path: /xyz/openbmc_project/sensors/voltage/PVNN_PCH_AUX

- name: sensor value group
  description: >
    'sensor value.'
  class: group
  group: property
  type: int64
  members:
    - interface: xyz.openbmc_project.Sensors.Value
      meta: VOLTAGE
      property: Value

- name: watch sensor value
  description: >
    'Trigger logic on sensor value.'
  class: watch
  watch: property
  paths: voltage sensor path group
  properties: sensor value group
  callback: sensor value count condition

- name: sensor value count condition
  description: >
    'check critical condition of the sensors.'
  class: condition
  condition: count
  paths: voltage sensor path group
  properties: sensor value group
  callback: value handler callback
  countop: '>'
  countbound: 0
  op: '>'
  bound: 10
 
- name: value handler callback
  description: >
    'value handler call back.'
  class: callback
  callback: group
  members:
    - example journal callback value

- name: example journal callback value
  description: >
    simple joural entry.'
  class: callback
  callback: journal
  paths: voltage sensor path group
  properties: sensor value group
  severity: INFO
  message: Hello world from PDM Value!

Best regards,

Wim

-----Original Message-----
From: Matt Spinler [mailto:mspinler at linux.ibm.com] 
Sent: Tuesday, April 9, 2019 3:51 PM
To: Wim Vervoorn <wvervoorn at eltan.com>; Lei YU <mine260309 at gmail.com>; Matthew Barth <msbarth at linux.ibm.com>
Cc: openbmc at lists.ozlabs.org
Subject: Re: using phosphor-dbus-monitor

Hi Wim,

If you could post your YAML somewhere, I could take a look for any obvious problems.

On 4/9/2019 2:23 AM, Wim Vervoorn wrote:
> Hello Lei,
>
> Thanks for your response. I know this example too and it helps a bit but it doesn’t really clarify all issues.
>
> As you've worked with this as well. Do you understand the meta item? The example indicates it has different meaning but doesn't provide any pointers to what those meanings are. Have you been able to find out?
>
> Best Regards,
> Wim Vervoorn
>
> -----Original Message-----
> From: Lei YU [mailto:mine260309 at gmail.com]
> Sent: Tuesday, April 9, 2019 5:44 AM
> To: Wim Vervoorn <wvervoorn at eltan.com>; Matthew Barth 
> <msbarth at linux.ibm.com>
> Cc: openbmc at lists.ozlabs.org
> Subject: Re: using phosphor-dbus-monitor
>
>> I am trying to use phosphor-dbus-monitor to create logging of sensor exceptions like a Critical state on a specific sensor.
>> I am able to create a solution with a building yaml but at the end it doesn’t deliver me the desired result.
>> As there are very limited examples (on a few in the witherspoon) it is very hard to figure out where the mistake is.
> There is an example yaml config in the repo:
> https://github.com/openbmc/phosphor-dbus-monitor/blob/master/src/examp
> le/example.yaml
>
> And I have the same feeling that it's hard to know what's wrong if 
> something is wrong.ei
>
>> Are there any tools that can be used to make this easier?
> @Matthew Barth Could you kindly help to add some doc/tool to make it easier to use?
>
>> Additionally is this the correct method to achieve this goal or should I use something else to define conditions for logging?
> I think so. This repo is intended to watch the dbus and do stuff as yaml config.
>
>