Tracking target build status via buck2 log show is unstable due to schema changes

[ztygod]

Hi Buck2 team,

I’m trying to track the execution status of individual targets during a build. The statuses I want to capture include:

• pending — waiting to be executed
• running — currently executing
• succeeded — finished successfully
• failed — execution failed
• skipped (optional) — cached or not executed

I attempted to use buck2 log show --json to parse target events, but I ran into the following warning:

"Warning: the schemas are all subject to change, so we do not recommend relying on the format. For the source of truth, take a look at data.proto."

My concern is that the log JSON output is unstable and may break with Buck2 upgrades, making it difficult to reliably track target states in a CI or monitoring system.

Questions / Requests:

1. Is there a recommended, stable way to track target execution status in real-time?
2. Can you provide guidance or an example on using data.proto / the event stream to achieve this?
3. Would it be possible to expose a stable JSON API or a “status summary” output for targets?

Thanks for your help!