Additional metrics abra could provide? #443
Open
opened 2023-04-11 20:32:24 +00:00 by decentral1se
·
0 comments
Labels
Clear labels
abra
awaiting-feedback
backups
bug
build
ci/cd
community organising
contributing
coopcloud.tech
design
documentation
duplicate
enhancement
fedi
fedi-infra
finance
funding
good first issue
help wanted
installer
legal
performance
proposal
question
security
test
wontfix
Everything to do with abra
Ping/pong on comms
Something is not working
Go build related issues
Getting the robots into the mix
Opening this thing up
Contributors stuff
Our main website
Design thinking required
Let's write things together
This issue or pull request already exists
New feature
Democratic decision making
Money things
Anything related to grant funding
Easy start with development
Need some help
Installation related issues
Performance related
Large change which requires feedback & decisin making
More information is needed
Securing our shit
Unit or integration test suite
This won't be fixed
No labels
enhancement
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
3wordchant
aadil (Aadil Ayub)
abra-bot (Abra Bot)
ammaratef45
amras (Sarma)
Apfelwurm
BornDeleuze
Brooke
carla
cas (Cassowary)
coopcloud
cyrnel
decentral1se (d1)
dede
devydave
fauno (fauno)
iexos
jade (Jade Ambrose)
jjsfunhouse
jmakdah2 (Jackie Makdah)
joe-irving (Joe Irving)
kawaiipunk (KawaiiPunk)
knoflook
kolaente
lambdabundesverband
linnealovespie (April)
moosemower
moritz
notplants
oxaliq (sorrel)
p4u1
pharaohgraphy (Andrew 🐦🔥❤️🔥✴️)
renovate-bot (Comrade Renovate Bot)
ripclap
simon
sixsmith (Sixsmith)
stevensting
trav (Trav Fryer)
val (val (he/him))
yksflip
Clear assignees
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: toolshed/organising#443
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
I've discovered a bunch more metrics that we could make use via
abra:the equivalent of
journalctl -fu docker.servicevia 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 statsafaiu. 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 infoafaiu. 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?