All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rahul Kapoor <rahulkapoor@microsoft.com>
To: "openbmc@lists.ozlabs.org" <openbmc@lists.ozlabs.org>
Subject: Redfish Message Registry
Date: Fri, 13 Nov 2020 21:21:53 +0000	[thread overview]
Message-ID: <MWHPR21MB15617F0E229621D95588880CABE60@MWHPR21MB1561.namprd21.prod.outlook.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1757 bytes --]

Hi,

Looking at bmcweb's message registry implementation  (openbmc_message_registry.hpp) I understand that each registry entry is purpose defined for a specific system event.
I am looking for a generic registry entry (other than SELEntryAdded)  that can be used for any discrete sensor and let the message arguments specify what discrete sensor it is associated with and other details. Following is what I am thinking

MessageEntry{"DiscreteSensorAlert_1",
                 {
                     "Indicates that a discrete sensor "
                     "has critical alert condition met."
                     "Additional information in Event"
                     "data 1",
                     "%1 discrete sensor raised alarm.\n"
                     "Error=%2 \nEvent Data1=%3",
                     "Critical",
                     3,
                     {"string", "string", "number"},
                     "Check the sensor or subsystem for errors.",
                 }},
    MessageEntry{"DiscreteSensorAlert_2",
                 {
                     "Indicates that a discrete sensor "
                     "has critical alert condition met"
                     "Additional information in Event"
                     "data 1 and 2",
                     "%1 discrete sensor raised alarm.\n"
                     "Error=%2 \nEvent Data1=%3 "
                    "Event Data2=%4",
                     "Critical",
                     4,
                     {"string", "string",
                      "number","number"},
                     "Check the sensor or subsystem for errors.",
                 }},

Message id is of the form <ID>_<Event data fields>

Let me know what you think

-Rahul Kapoor


[-- Attachment #2: Type: text/html, Size: 7494 bytes --]

             reply	other threads:[~2020-11-13 21:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-13 21:21 Rahul Kapoor [this message]
2020-11-13 22:01 ` Redfish Message Registry Ed Tanous

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=MWHPR21MB15617F0E229621D95588880CABE60@MWHPR21MB1561.namprd21.prod.outlook.com \
    --to=rahulkapoor@microsoft.com \
    --cc=openbmc@lists.ozlabs.org \
    /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.