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

"auth0 logs tail" date field is useless #418

Closed
joshw opened this issue May 4, 2022 · 2 comments
Closed

"auth0 logs tail" date field is useless #418

joshw opened this issue May 4, 2022 · 2 comments
Labels
feature request A feature has been asked for or suggested by the community

Comments

@joshw
Copy link

joshw commented May 4, 2022

Description

Each line in the auth0 logs tail output includes a Date column formatted as as a relative time.

"2 seconds ago" is computed relative to the log message vs the time that the message is displayed. This makes sense for log queries, but in tail mode, it produces completely useless values (always a few seconds ago) It needs to show absolute time instead.

Reproduction

auth0 logs tail

produces lines such as

Success Exchange           Client Credentials for Access Token                       2 seconds ago        N/A                     ClientName

It should show something along the lines of this instead:

Success Exchange           Client Credentials for Access Token                       2022-05-03T21:47:08.899Z        N/A                     ClientName

Environment

Please provide the following:

  • Version of this library used:
% auth0 --version
auth0 version 0.11.7 f9bcaf1b0d5c6c380022842b9707dfb8620b4890
  • Version of the platform or framework used, if applicable:

n/a

  • Other relevant versions (language, server software, OS, browser):
Darwin  20.6.0 Darwin Kernel Version 20.6.0: Wed Jan 12 22:22:42 PST 2022; root:xnu-7195.141.19~2/RELEASE_X86_64 x86_64
  • Other modules/plugins/libraries that might be involved:

n/a

@sergiught sergiught added the enhancement An enhancement or improvement to the SDK that could not be otherwise categorized as a new feature label May 5, 2022
@sergiught sergiught added feature request A feature has been asked for or suggested by the community and removed enhancement An enhancement or improvement to the SDK that could not be otherwise categorized as a new feature labels Oct 10, 2022
@willvedd
Copy link
Contributor

Update: We've included fix for this in the v1.0.0-beta.1 release. For those who are so inclined, we'd be happy to receive feedback on the beta before it goes GA, including feedback on this particular issue. Otherwise, we plan to close this issue out once v1.0.0 reaches GA. Again, appreciate everyone's patience!

@willvedd
Copy link
Contributor

Fixed and released in our v1.0.0 release. We encourage folks to upgrade and give it a shot!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature request A feature has been asked for or suggested by the community
Projects
None yet
Development

No branches or pull requests

3 participants