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

Multi-Sink #721

Open
Crypto2099 opened this issue Dec 13, 2023 · 1 comment
Open

Multi-Sink #721

Crypto2099 opened this issue Dec 13, 2023 · 1 comment

Comments

@Crypto2099
Copy link

It would be great to be able to potentially have multiple sinks and/or some way of recording status to terminal when running Oura in daemon mode (potentially as a service) so that tools like the terminal window or journalctl could be used to verify that Oura is running and its current height easily even while sinking to something like a webhook. Particularly if the selection criteria may be few and far between, it would be nice to have a health/status check without needing to consult a full-scale Prometheus/Grafana dashboard.

@scarmuega
Copy link
Member

hi @Crypto2099,

Regarding multiple sinks, we've analyzed this option and found that there're a lot of complex edge cases when using multiple sinks. The top one is how to handle "back-pressure" when one sink is slower than the other. We decided that the recommended way to handle this is to have multiple Oura instances where devs can configure each pipeline independently. Since each instance is relatively lightweight, there's not much overhead in running multiple.

Regarding recording status, Oura already provides several logs when running in daemon mode. In Oura v1, this output is controlled by the RUST_LOG env variable. Let me know if this is what you were looking for.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants