)]}'
{
  "commit": "a170a6bc4a9c1fbde23e4cda2cbd9dd16aba094f",
  "tree": "f71004890f7ea565db6943ebf8a9aa60a9f56d42",
  "parents": [
    "fd330819a099f0f2cc420ce5bad3f227e31d74fa"
  ],
  "author": {
    "name": "Eric Yang",
    "email": "eric.yang.wiwynn@gmail.com",
    "time": "Fri Jan 30 05:48:00 2026 +0000"
  },
  "committer": {
    "name": "Amithash Prasad",
    "email": "amithash@meta.com",
    "time": "Thu Feb 12 03:07:24 2026 +0000"
  },
  "message": "meta-facebook: bmcweb: Move EventLog to Managers\n\nEnable PACKAGECONFIG \u0027redfish-eventlog-managers\u0027 for all meta-facebook\nplatforms to relocate EventLog from Systems to Managers resource.\n\nEventLog service location changes from:\n  /redfish/v1/Systems/\u003csystem-id\u003e/LogServices/EventLog/Entries\nto:\n  /redfish/v1/Managers/\u003cmanager-id\u003e/LogServices/EventLog/Entries\n\nMotivation:\nAs discussed in bmcweb commit \"Add Journal EventLog to Manager\" [1],\non multi-host platforms each ComputerSystem should ideally have\nseparate EventLogs to clearly distinguish events from different host\nnodes. However, the current implementation does not support per-host\nlog splitting - all events are logged to a single shared log.\n\nPlacing this shared log under a specific ComputerSystem creates\nsemantic ambiguity about which host\u0027s events are represented. When\nexperimental-redfish-multi-computer-system is enabled, bmcweb excludes\nEventLog from the Systems resource at compile time[1], making EventLog\ninaccessible without explicit Managers placement.\n\nThe Managers resource provides a semantically correct location because:\n- BMC Manager is the entity collecting and managing all system events\n- EventLog under Managers represents all events collected by the BMC\n- For multihost platforms, it represents events across all host nodes\n- Applying this to all meta-facebook platforms (both single-host and\n  multihost) ensures consistent EventLog location across the entire\n  meta layer\n- Access remains consistent regardless of which ComputerSystems exist\n  at runtime\n\nImplementation uses PACKAGECONFIG to enable the\nredfish-eventlog-managers option, which sets the bmcweb meson option\n\u0027redfish-eventlog-location\u0027 to \u0027managers\u0027 (default is \u0027systems\u0027).\nThis approach allows platform layers to control EventLog placement via\nstandard PACKAGECONFIG mechanism rather than directly manipulating meson\noptions.\n\nReference:\n[1] https://gerrit.openbmc.org/c/openbmc/bmcweb/+/83351\n\nChange-Id: I800d612be18fa9b7c0a2c35020afa6072fca734b\nSigned-off-by: Eric Yang \u003ceric.yang.wiwynn@gmail.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "c694dfdda76b658dc808f102b41e264b888e3560",
      "old_mode": 33188,
      "old_path": "meta-facebook/recipes-phosphor/interfaces/bmcweb_%.bbappend",
      "new_id": "f830f91047afaacd5ee288b1585dfe13bb369c66",
      "new_mode": 33188,
      "new_path": "meta-facebook/recipes-phosphor/interfaces/bmcweb_%.bbappend"
    }
  ]
}