System Logging and Monitoring
- Ashhad Alam
Adeptia Connect supports the centralized logging to track and visualise the system level logs generated by each micro-service from a single unified place. All the Microservices in Adeptia Connect writes its logs to standard output and standard error streams which ensures that the logs can be collected from a central location and can be visualised by any external logging solutions like EFK stack.
Adeptia Connect also supports the centralised monitoring to track and monitor the system level health and statuses. You can use Prometheus and Grafana for monitoring the Adeptia Connect resources. Adeptia also provides the following ready to use dashboards that can be imported directly to Grafana UI.
- JVM: Provides information about:
JVM memory
Process memory (provided by micrometer-jvm-extras)
CPU-Usage, Load, Threads, Thread States, File Descriptors, Log Events
JVM Memory Pools (Heap, Non-Heap)
Garbage Collection
Classloading
- Kubernetes Nodes: Dashboard to get an overview of one kubernetes node.Kubernetes dashboard to track node specific metrics: Idle CPU, System load, Memory Usage, Disk I/O, Disk space usage, Network received/transmitted
- Kubernetes Persistent Volumes usage: Gives insight of PV usage.
- Database Connection Pool: Provides information about pool size, active connections and idle connections from backend and log database per micro-service instance.
- Thread Info: Provides information about live thread count, peak thread count, dead lock thread count and thread states per micro-service instance.