awslogs
awslogs copied to clipboard
Watch is not working as expect
"get -w" gets just stuck.
Edit: the fork https://github.com/blueyed/awslogs/tree/fix-watch of @blueyed works pretty fine. He's sent a pull request. Any hope to see it merged anytime soon? Thanks
Same for me, not sure what changed (something got updated?) but --watch stopped working for me recently.
@w4pp Not using my branch I assume? Can you try it?
I am going to bite the bullet and try to submit a patch for this issue in the following weeks.
Is there some idea about what broke the --watch? I took a look on code and it looks good.
@marceloavan It's an old issue - have not checked recent code - is it fixed? Have you checked / seen https://github.com/jorgebastida/awslogs/pull/196 ? (the branch mentioned above)
@blueyed thank you for replay... I took a look on your PR and I will do some tests.
There is some idea about when this fix will be released?
I'm getting this too. It was working yesterday
@adeperio Check my comment above. Also more information would be useful - we cannot know if you only started using it yesterday, or since years already. The issue is about it breaking after running for a while. But the issue is known, so no need really to provide that info now - but just wanted to mention it since you triggered a notification for me (and others) anyway.
Thanks @blueyed I'll take a look
In terms of more info. I have been using
awslogs get [loggroup] ALL --watch
pretty reliably for the last few months.
Yesterday it had been working fine. Today this morning for some reason it had stopped working. I don't think it's application code as I've rolled back to previous versions etc to rule this out.
When I run the above command, nothing gets displayed to the console, and it just hangs there before I have to Ctrl+C out.
Even if I run this:
awslogs get [loggroup] ALL
awslogs doesn't display anything. So I don't think it's a problem with just the watch function.
I've checked my AWS credentials config and that all seems to be checking out and my connection and AWS resources are accessible and available.
Curiously though, if I run this:
awslogs get [log_group] --start='2h ago' --watch
I get logs displayed, but no new watch events get displayed. Would this have something to do with the issue that you had linked in your previous comment?
Not sure what other trouble shooting steps I could take?
I've also tried uninstalling and reinstalling awslogs, but still no joy
I started getting the same issue for one of my log groups but not another. I tried upgrading awscli and to the newest awslogs and it still has the same issue.
Not helpful.. /unsubscribe (also not helpful - but at least I provided a PR to fix it ;))