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

Not printing log messages anymore #37

Open
nerixim opened this issue Jan 15, 2023 · 3 comments
Open

Not printing log messages anymore #37

nerixim opened this issue Jan 15, 2023 · 3 comments

Comments

@nerixim
Copy link

nerixim commented Jan 15, 2023

Hi, thanks for your app 👍
I found it about 6 months ago, and it worked like a charm.

I tried using it again but it doesn't work as expected. The version hasn't changed since then so something may have changed in Cloudwatch API.

  • executing without options
$ utern /log/group
+ /log/group
# nothing beyond that
  • getting logs from before 1 hour

It's printing the logs until the present moment but no real-time updates (watching)

$ utern --since 1h /log/group
+ /log/group
+ /log/group › log/stream/id (2023-01-14T16:46:07+00:00)
# some logs as expected
# ... producing new logs
# no more input
@tomat
Copy link

tomat commented Jan 16, 2023

Same problem here, been like this for at least a couple of weeks

  1. Can't get very recent events unless I get 10m or more, i e 1m won't work but 10m will show 10m of data including up to now
  2. Not getting new events after the initial get, but watch not working, as mentioned above

No Cloudwatch-related changes to my AWS setup. I tried deleting old empty log groups but did not make a difference.

@tomat
Copy link

tomat commented Jan 16, 2023

Doing some debugging and reading AWS docs I found that the LastEventTimestamp is indeed updated "slowly", docs say:

"The lastEventTime value updates on an eventual consistency basis. It typically updates in less than an hour from ingestion, but in rare situations might take longer."

Code comments seem to imply that instead LastIngestionTime is used, since it should update faster, but the docs for that also say:

"It typically updates in less than an hour after ingestion, but in rare situations might take longer."

Will try to check if it is indeed updating more slowly than usual for some reason, but I think that could be the problem

@tomat
Copy link

tomat commented Jan 16, 2023

The ListStreams function is filtering based on LastIngestionTime, so it won't even tail streams until the ingestion time is updated

Also confirmed that LastIngestionTime is not updating "live", in my case it seems to be in sync with LastEventTimestamp right now

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