Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Monitor cloud events #29

Closed
brooksmtownsend opened this issue Jun 7, 2021 · 1 comment
Closed

Monitor cloud events #29

brooksmtownsend opened this issue Jun 7, 2021 · 1 comment
Labels
status quo Issues containing work to maintain feature parity with the existing version

Comments

@brooksmtownsend
Copy link
Member

Related to #6

We publish CloudEvents for things like provider_started, actor_started, provider_stopped, and more after the above issue. We should have a module that can be instantiated and monitor for these types of events, similar to what was implemented in wasmCloud/wasmCloud#183.

The goal of such a module would be to provide a way to monitor events that occur in a wasmcloud host / lattice, which could either be used to replay events leading up to an issue or assert that specific events had occurred. For example, when we write tests that start a provider, we can ensure that the provider has had enough time to spawn as a process and is ready for invocations.

@brooksmtownsend brooksmtownsend added the status quo Issues containing work to maintain feature parity with the existing version label Jun 7, 2021
@autodidaddict autodidaddict removed this from To do in wasmCloud OTP RC0 Jul 15, 2021
@stevelr
Copy link
Contributor

stevelr commented Aug 16, 2021

taken care of by other issues

@stevelr stevelr closed this as completed Aug 16, 2021
wasmCloud 1.0-RC0 automation moved this from To do to Done Aug 16, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status quo Issues containing work to maintain feature parity with the existing version
Projects
No open projects
Development

No branches or pull requests

2 participants