checkmk-docs VS Grafana

For this, you can use checkmk to monitor wifi, physical servers, vms and services (sql, app, etc). You can find more details: https://docs.checkmk.com

With checkmk you can also monitor the bandwidth of every interface in the equipment, cpu, ram and many other aspects(bgp, tunnels, sessions, etc). You can send notifications if you need and also you can create maps with the devices locations using embedded nagvis and show them on a tv. Further you can monitor all servers, applications, kubernetes, clouds. Basically, checkmk is a full monitoring solution that will help you to know at every moment what is happening in your environment. You can take a look at https://docs.checkmk.com/

For networking area, you can monitor routers, switches, vpns, etc. through snmp or special agents (api) and for servers through agent or special agents depending on the purpose. Overalll there are more than 2000 monitoring plugins available by default and these can be exetended easily. Take a look here: https://docs.checkmk.com

For monitoring area i’m using checkmk. You can monitor many types of server, applications, logs and everything else needed (networking, hardware, sensors) and even cloud integrations. If you want to use also graphana, you can export metrics or use the graphana plugin for checkmk. You have more than 2000 plugins available. You can look at https://docs.checkmk.com

Hi, for monitoring fortinet devices i had great success with checkmk. I monitored all the interfaces, signature, ram, memory, vpn tunnels. For the access points themselves, you can use snmp monitoring from checkmk in orde rto get all the necessary data(interface, cpu, ram). For the interface, normally you should obtain speed and errors which is important. You can create dashboards and maps to properly display the information on a tv and also use the notification integrations. You can check for more details https://docs.checkmk.com/

For more info about checkmk you can check https://docs.checkmk.com/ and https://checkmk.com/integrations/ for a full list of plugins and supported devices/services/servers

We are at the moment migrating our docs to GitHub: https://github.com/tribe29/checkmk-docs

Speaking of metrics and Grafana, this popular project gets a major update too. As shown in the image above, Grafana is a data visualisation and composable observability platform. With Grafana you can query, visualise, alert on, and understand your metrics wherever that data may sit. The latest update adds lots of new features and enhancements such as a slightly refreshed UI, reducing the set of fields that could trigger an alert state change, the removal of Loki's API restrictions on resource calls, and lots more. Check out all the changes in the changelog.

Implement health checks and monitoring to ensure the availability and performance of your microservices. Use tools like Prometheus, Grafana, or NestJS built-in health checks.

In this article, we’ll look at one of the ways to monitor the InterSystems IRIS data platform (IRIS) deployed in the Google Kubernetes Engine (GKE). The GKE integrates easily with Cloud Monitoring, simplifying our task. As a bonus, the article shows how to display metrics from Cloud Monitoring in Grafana.

Kubernetes Documentation: https://kubernetes.io/docs/home/ Kubernetes Tutorials: https://kubernetes.io/docs/tutorials/ Kubernetes Community: https://kubernetes.io/community/ Prometheus: https://prometheus.io/ Grafana: https://grafana.com/ Elasticsearch: https://www.elastic.co/elasticsearch/ Kibana: https://www.elastic.co/kibana Helm: https://helm.sh/ Prometheus Helm Chart: https://github.com/prometheus-community/helm-charts/tree/main/prometheus Grafana Helm Chart: https://github.com/grafana/helm-charts/tree/main/grafana Elasticsearch Helm Chart: https://github.com/elastic/helm-charts/tree/main/elasticsearch Kibana Helm Chart: https://github.com/elastic/helm-charts/tree/main/kibana RBAC: https://kubernetes.io/docs/reference/access-authn-authz/rbac/ Network Policies: https://kubernetes.io/docs/concepts/services-networking/network-policies/ StatefulSets: https://kubernetes.io/docs/concepts/workloads/controllers/statefulset/ DaemonSets: https://kubernetes.io/docs/concepts/workloads/controllers/daemonset/ Taints and Tolerations: https://kubernetes.io/docs/concepts/scheduling-eviction/taint-and-toleration/ Custom Resource Definitions (CRDs): https://kubernetes.io/docs/concepts/extend-kubernetes/api-extension/custom-resources/ Operators: https://kubernetes.io/docs/concepts/extend-kubernetes/operator/

Monitoring application logs is a crucial aspect of the software development and deployment lifecycle. In this post, we'll delve into the process of observing logs generated by Docker container applications operating within HashiCorp Nomad. With the aid of Grafana, Vector, and Loki, we'll explore effective strategies for log analysis and visualization, enhancing visibility and troubleshooting capabilities within your Nomad environment.

To help us visualize these scenarios, we'll build a Grafana Dashboard so we can follow along.

Visualization and Analysis: Choose a tool with intuitive and customizable dashboards, charts, and visualizations. A question to ask is, "Are the visualization features of this tool user-friendly and adaptable to our team's specific needs?" Tools like Grafana and Kibana provide powerful visualization capabilities.

Prometheus: Open-source monitoring system. Often used together with Grafana.