Additional metrics abra could provide? #443
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
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: coop-cloud/organising#443
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?
I've discovered a bunch more metrics that we could make use via
abra
:the equivalent of
journalctl -fu docker.service
via https://pkg.go.dev/github.com/docker/docker/client#Client.Events which we could stream viaabra server logs
? This is logs of every deployed container and the daemon and containerd logs merged together. Good to poll when something is really going wrong on the serveran entire disk usage report via https://pkg.go.dev/github.com/docker/docker/client#Client.DiskUsage! there are options to specicfy, e.g. only volumes, only images, etc. this is a pretty costly operation for large deployments but could be useful. perhaps a
abra server disk
?per-container stats via https://pkg.go.dev/github.com/docker/docker/client#Client.ContainerStats which is the equivalent of
docker stats
afaiu. that would be handy to gather resource usage on a pretty fine-grained level viaabra
. that could be uhmmmabra app stats
?we can also poll general docker daemon info via https://pkg.go.dev/github.com/docker/docker/client#Client.Info e.g. docker version which is
docker info
afaiu. maybe aabra server info
?These could be cool and simple to add! I certainly use them via the Docker CLI quite a bit and would deffo like the convenience via
abra
. The code to wrap them is pretty trivial, so it's mostly a bitta CLI UI/UX work and testing.Additional metrics we could add to abrato Additional metrics abra could provide?