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

astro cli logs --log-count parameter behavior gap #1736

Open
1 of 3 tasks
sakethsomaraju opened this issue Oct 22, 2024 · 0 comments
Open
1 of 3 tasks

astro cli logs --log-count parameter behavior gap #1736

sakethsomaraju opened this issue Oct 22, 2024 · 0 comments

Comments

@sakethsomaraju
Copy link

sakethsomaraju commented Oct 22, 2024

Describe the bug

Using CLI to get component logs with astro deployment logs --scheduler --log-count 100000000 but could only get ~600 lines of logs where expectation is to get all logs within 24hrs.

The above command, it returns logs within last ~75 minutes or limiting to 700-800 lines where count passed is 1000000. Given that, there are 9000+ logs in UI

$ astro deployment logs  "cm2eph2dt0o8t01m1zohatsu9" --log-count 10000000 --scheduler  | wc       
     752    7384  103148

What CLI Version did you experience this bug?

This CLI bug is related to which Astronomer Platform?

  • Astro
  • Software
  • None/Unknown

What Operating System is the above CLI installed on?
Mac OS
🪜 Steps To Reproduce

  1. Create a deployment with astro cli.
  2. Wait for 6 hours for logs to accumulate from the default dag which is already present.
  3. Check for logs with astro deployment logs deploymentid --log-count 10000000 --scheduler, could get only last 75 minutes logs.

📸 Screenshots

Not Applicable

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

1 participant