You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since health check events are by nature self-healing events (if you miss one, just wait for the next one; it'll be along soon), it may be desirable to send them over a non-streaming NATS connection, which will reduce storage concerns on the Automate side.
I don't think it's possible to send non-streaming messages using a streaming NATS client, but if it is, that would be ideal. Otherwise, we probably need to manage two separate connections.
We'll want to do this work alongside the Automate team to ensure that such changes would be worth the effort to implement them.
The text was updated successfully, but these errors were encountered:
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. We value your input and contribution. Please leave a comment if this issue still affects you.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. We value your input and contribution. Please leave a comment if this issue still affects you.
This issue has been automatically closed after being stale for 400 days. We still value your input and contribution. Please re-open the issue if desired and leave a comment with details.
Since health check events are by nature self-healing events (if you miss one, just wait for the next one; it'll be along soon), it may be desirable to send them over a non-streaming NATS connection, which will reduce storage concerns on the Automate side.
I don't think it's possible to send non-streaming messages using a streaming NATS client, but if it is, that would be ideal. Otherwise, we probably need to manage two separate connections.
We'll want to do this work alongside the Automate team to ensure that such changes would be worth the effort to implement them.
The text was updated successfully, but these errors were encountered: