astro cli logs --log-count parameter behavior gap

[sakethsomaraju]

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?

• [X] 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

[AmFlint]

We need to evaluate whether the experienced behavior is expected, and either update the doc on the command or fix the bug