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.

Sign up for GitHub

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

Jump to bottom

More visibility of NATS connectivity failures #1185

Open
Yshayy opened this issue Dec 23, 2019 · 0 comments
Open

More visibility of NATS connectivity failures #1185

Yshayy opened this issue Dec 23, 2019 · 0 comments
Labels
bug good first issue production quality services/api

Comments

@Yshayy
Copy link
Contributor

Yshayy commented Dec 23, 2019 •
edited

Currently, if NATS is down or unreachable, Tweek api will be stuck trying reconnecting without any indication (on boot). Adding logs can help making such a problem much easier to debug.

Update
NatsVersionProvider should write log on disconnection failure (https://github.com/Soluto/tweek/blob/master/core/Engine/Tweek.Engine.Drivers/Rules/NatsVersionProvider.cs#L32), this requires some investigation
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug good first issue production quality services/api
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@Yshayy