abra app logs does not show log entries in correct chronological order #416
Labels
No Label
abra
abra-gandi
awaiting-feedback
backups
bug
build
ci/cd
community organising
contributing
coopcloud.tech
democracy
design
documentation
duplicate
enhancement
finance
funding
good first issue
help wanted
installer
kadabra
performance
proposal
question
recipes.coopcloud.tech
security
test
wontfix
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: coop-cloud/organising#416
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Don't know how this happens, but I saw this already quite some times using abra app logs. Maybe another dead container that shows up here? Would be super helpful for debugging stuff to have this in order :)
(Also not sure if bug or feature request? :D)
An example:
edit: make example more clear
@yksflip
Righhht, so, for context, there was no "off the shelf" API for "give me all the logs", so I had to cook up a concurrent "stream everything you can from every service and merge them into a single stdout/stderr stream" which is
abra app logs
today 🙃Are we specifically speaking about out of order timestamps here? I think that is probably just a bug. I think I see out of order timestamps at least, in the millisecs?
Or are we talking about somehow stream all logs from all services but then "mixing" them in a less chaotic manner?
It could be that the logs from the services that appear to have out of order timestamps are just streaming in at weird times due to things like network or service latency...
ah okayy, I think I get it now ... I think what happened was:
still see the logs of the broken service mixed in (almost 1h difference)
but yeah maybe thats just good enough for now and better logging are part of the monitoring stack :D
Aha, I see. Perhaps we could make an improvement here. I see that there is a
Since
option we're not making use of but could? Maybe this could be configured from the CLI? See https://pkg.go.dev/github.com/docker/docker@v23.0.1+incompatible/api/types#ContainerLogsOptions for the options. Seeeec6469ba1/cli/app/logs.go (L22)
for options we do set.yeah, that could be somehting! I gave it a try here: coop-cloud/abra#276
seems to just work!