Cockpit vs Grafana Loki+Promtail #21330
Unanswered
FAUSTMANNSTEF
asked this question in
Q&A
Replies: 1 comment 2 replies
|
Cockpit's metrics and logs are per host and have no reporting / tracking capabilities nor will they because you can only view your logs when you connect to Cockpit there is no background daemon. In short:
|
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Hey guys !
I am currently working on a project aimed to monitor servers from a centralized environment and i came across cockpit .
I can already see that cockpit works amazingly for monitoring a servers performance ( system health checks , error logs, warning logs etc.). However i was wondering if i can use cockpit instead of grafana to adress these issues :
Insight into Nginx logs ( clear view of both old and new Nginx Access and Error logs + monitor any other additional services running on the server )
Monitor docker internal and service logs (gain insight into the docker engine + applications running within docker containers.
Freedom for custom logs for project specific stuff i would like to monitor ( is Cockpit bound to specific logs or can i delve deeper into more detailed/custom stuff if i wanted to? )
Can cockpit run alongside each project on the server it is hosted on? in case i would like to monitor multiple projects from a centralized environment ?.
Is it scalable ? ( if i create a new project which i would like to monitor is it easy to integrate with the existing cockpit setup that contains projects
Ability to set up trackers and slack integration ? ( We aim to set up trackers for our APIs to check on data accessibility and CVE trackers for the supporting software we use in our projects . Would it also be possible to integrate central logging into slack ?
Thank you very much for your time guys !
I appreciate any source or answer regarding this post !
All reactions