Add event struct; add events field to AgentDeployment

[andrewnitu]

No description provided.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 96b285b

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

💥 An error occurred when fetching the changed packages and changesets in this PR

Some errors occurred when validating the changesets config:
The package or glob expression "github.com/livekit/protocol" specified in the `fixed` option does not match any package in the project. You may have misspelled the package name or provided an invalid glob expression. Note that glob expressions must be defined according to https://www.npmjs.com/package/micromatch.

[andrewnitu]

ref AP-271

[yoonsio]

Is this expected to be consumed by livekit-cli?

[yoonsio]

Given we have observability events support coming soon, should we just log the events for now?

[andrewnitu]

yup, the code is not final but it's consumed here https://github.com/livekit/livekit-cli/pull/753/files#diff-4a70574ec74b4fc8888fd29a16e49065fec8bd1833148322247a5522810a1c89R845

[andrewnitu]

@yoonsio who is leading this? Let me speak with them to understand if it can fit our use case. We could be publishing quite a decent QPS in the future, so it would need to handle that.

[yoonsio]

I don't think it is necessary to show events via livekit-cli given that it can be noisy with crashlooping pods. I think displaying aggregated status should be enough and we can follow up with separate API to show the events.

[yoonsio]

You can ask in #project-agent-observability channel.