All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matt Spinler <mspinler@linux.ibm.com>
To: Wim Vervoorn <wvervoorn@eltan.com>, Lei YU <mine260309@gmail.com>,
	Matthew Barth <msbarth@linux.ibm.com>
Cc: "openbmc@lists.ozlabs.org" <openbmc@lists.ozlabs.org>
Subject: Re: using phosphor-dbus-monitor
Date: Tue, 9 Apr 2019 08:50:36 -0500	[thread overview]
Message-ID: <0f2fc6f7-be66-ab65-7b90-b0bdd45d5fcd@linux.ibm.com> (raw)
In-Reply-To: <bdc0e08ece734d44b8eebad84eb5db35@Eltsrv03.Eltan.local>

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@gmail.com]
> Sent: Tuesday, April 9, 2019 5:44 AM
> To: Wim Vervoorn <wvervoorn@eltan.com>; Matthew Barth <msbarth@linux.ibm.com>
> Cc: openbmc@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/example/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.
>
>

  reply	other threads:[~2019-04-09 13:50 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-08 13:42 using phosphor-dbus-monitor Wim Vervoorn
2019-04-09  3:44 ` Lei YU
2019-04-09  7:23   ` Wim Vervoorn
2019-04-09 13:50     ` Matt Spinler [this message]
2019-04-09 13:59       ` Wim Vervoorn
2019-04-09 14:12       ` Matthew Barth
2019-04-09 14:22         ` Wim Vervoorn
2019-04-10 14:27         ` Wim Vervoorn
2019-04-11 12:38           ` Lei YU
2019-04-11 13:05             ` Wim Vervoorn
2019-04-11 16:26               ` Matt Spinler

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=0f2fc6f7-be66-ab65-7b90-b0bdd45d5fcd@linux.ibm.com \
    --to=mspinler@linux.ibm.com \
    --cc=mine260309@gmail.com \
    --cc=msbarth@linux.ibm.com \
    --cc=openbmc@lists.ozlabs.org \
    --cc=wvervoorn@eltan.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.