Difference between revisions of "Monitoring"
Jump to navigation
Jump to search
↑ https://www.freedesktop.org/software/systemd/man/systemd-cgtop.html
| (28 intermediate revisions by 5 users not shown) | |||
| Line 1: | Line 1: | ||
[[wikipedia:Monitoring]] systems are responsible to collect, show and generate alarms in monitored devices. | [[wikipedia:Monitoring]] systems are responsible to collect, show and generate alarms in monitored devices. | ||
| − | |||
* Performance tools: | * Performance tools: | ||
** [[Memory]]: <code>[[vmstat]]</code>, <code>free</code>, <code>[[sar -r]]</code> | ** [[Memory]]: <code>[[vmstat]]</code>, <code>free</code>, <code>[[sar -r]]</code> | ||
** Disk tools: <code>iostat</code>, <code>[[iotop]]</code>, <code>[[hdparm]]</code>, <code>[[sar -d]]</code>, <code>[[ionice]]</code>, <code>[[hdparm]]</code>, <code>[[badblocks]]</code> and <code>dd</code> | ** Disk tools: <code>iostat</code>, <code>[[iotop]]</code>, <code>[[hdparm]]</code>, <code>[[sar -d]]</code>, <code>[[ionice]]</code>, <code>[[hdparm]]</code>, <code>[[badblocks]]</code> and <code>dd</code> | ||
| − | ** [[Network]]: <code>[[ntop]], [[nmap]], [[ping]], [[fping]], ncat, [[mtr]], [[traceroute]], [[tracepath]], [[vnstat]]</code> | + | ** [[Network monitoring|Network]]: <code>[[ntop]], [[nmap]], [[ping]], [[fping]], ncat, [[mtr]], [[traceroute]], [[tracepath]], [[vnstat]]</code> |
** [[Kernel]]: [[perf]], strace, [[ftrace]], [[Dtrace]] | ** [[Kernel]]: [[perf]], strace, [[ftrace]], [[Dtrace]] | ||
** [[cgroups]] and [[docker]]: <code>[[systemd-cgtop]]</code><ref>https://www.freedesktop.org/software/systemd/man/systemd-cgtop.html</ref>, <code>[[docker stats]]</code> | ** [[cgroups]] and [[docker]]: <code>[[systemd-cgtop]]</code><ref>https://www.freedesktop.org/software/systemd/man/systemd-cgtop.html</ref>, <code>[[docker stats]]</code> | ||
| Line 15: | Line 14: | ||
* [[Nagios]] ([[2002]]) | * [[Nagios]] ([[2002]]) | ||
* [[munin]] (2003) | * [[munin]] (2003) | ||
| + | * [[PRTG]] (2003) (Windows, propietary) | ||
* [[Check MK]] (2008) | * [[Check MK]] (2008) | ||
* [[Icinga]] ([[2009]]), [[Nagios]] fork | * [[Icinga]] ([[2009]]), [[Nagios]] fork | ||
| Line 23: | Line 23: | ||
* [[monit]] | * [[monit]] | ||
* [[Glances]] ([[2011]]) | * [[Glances]] ([[2011]]) | ||
| + | * [[Checkmk]] (2008) | ||
== Monitoring Services == | == Monitoring Services == | ||
| − | * [[OpsGenie]] ([[Atlassian]]) | + | * [[OpsGenie]] ([[Atlassian]] [https://www.google.com/finance/quote/TEAM:NASDAQ TEAM:NASDAQ]) |
| − | * [[Pingdom]] ([[SolarWinds]]) | + | * [[Pingdom]] (2005) ([[SolarWinds]]) |
| − | * [[ | + | * [[AWS CloudWatch]]: <code>[[amazon-cloudwatch-agent]]</code> |
| − | * [[ | + | * [[GCP monitoring]]: <code>[[gcloud monitoring]]</code> |
| + | * [[Azure Monitor]] | ||
* [[PagerDuty]] (2009) | * [[PagerDuty]] (2009) | ||
| + | * [[New Relic]] (2008, [https://www.google.com/finance/quote/NEWR:NYSE?window=MAX NEWR:NYSE]) | ||
| + | * [[Datadog]] (2010, [https://www.google.com/finance/quote/DDOG:NASDAQ?window=MAX DDOG:NASDAQ]) | ||
| + | * [[Skylight.io]] | ||
| + | * [[LogicMonitor]] | ||
== Related terms == | == Related terms == | ||
| − | * [[ | + | * [[On-Call]] |
* [[Notifications]] | * [[Notifications]] | ||
| + | * [[Sensu]] multicloud monitoring | ||
* [[Stackstate]] | * [[Stackstate]] | ||
* [[AIOps]] | * [[AIOps]] | ||
* [[Metric colletion tools]] | * [[Metric colletion tools]] | ||
| − | * [[Understand how to monitor applications in Kubernetes | + | * [[Kubernetes monitoring]] ([[CKA]]: [[Understand how to monitor applications in Kubernetes]]) |
* [[SLA Management Monitoring Tools]] | * [[SLA Management Monitoring Tools]] | ||
| + | * [[CAdvisor]] container monitoring | ||
| + | * [[Observability]] | ||
== See also == | == See also == | ||
* {{Monitoring software}} | * {{Monitoring software}} | ||
| − | |||
* [[Security information and event management]] (SIEM) | * [[Security information and event management]] (SIEM) | ||
* {{Performance}} | * {{Performance}} | ||
* {{monitoring}} | * {{monitoring}} | ||
| + | * {{Architecture}} | ||
[[Category:Monitoring]] | [[Category:Monitoring]] | ||
Latest revision as of 09:19, 25 October 2023
wikipedia:Monitoring systems are responsible to collect, show and generate alarms in monitored devices.
- Performance tools:
- Troubleshooting tools:
cfg2html,ansible-cmdb,sysreport, sosreport andacct
Monitoring tools[edit]
- Zabbix (2001)
- Cacti (2001)
- Nagios (2002)
- munin (2003)
- PRTG (2003) (Windows, propietary)
- Check MK (2008)
- Icinga (2009), Nagios fork
- Prometheus (2012, Go): Prometheus alertmanager, Prometheus node exporter
- Netdata (2013)
- Spiceworks (2014)
- Tivoli Monitoring
- monit
- Glances (2011)
- Checkmk (2008)
Monitoring Services[edit]
- OpsGenie (Atlassian TEAM:NASDAQ)
- Pingdom (2005) (SolarWinds)
- AWS CloudWatch:
amazon-cloudwatch-agent - GCP monitoring:
gcloud monitoring - Azure Monitor
- PagerDuty (2009)
- New Relic (2008, NEWR:NYSE)
- Datadog (2010, DDOG:NASDAQ)
- Skylight.io
- LogicMonitor
Related terms[edit]
- On-Call
- Notifications
- Sensu multicloud monitoring
- Stackstate
- AIOps
- Metric colletion tools
- Kubernetes monitoring (CKA: Understand how to monitor applications in Kubernetes)
- SLA Management Monitoring Tools
- CAdvisor container monitoring
- Observability
See also[edit]
- Monitoring: Prometheus, Cacti, monit, munin, RRDtool, Zabbix, Netdata, Nagios, Check MK, Icinga, Pingdom, OpsGenie and Datadog, Opsgenie, PRTG, Checkmk
- Security information and event management (SIEM)
- Performance, monitoring, sysstat, metrics, Telemetry
- Monitoring: On call, Monitoring software, Monitoring services, Resource monitoring, Metric colletion tools, network monitoring, SLA Management Monitoring Tools, Alarm/Alert, Resource starvation, Alerts and notifications, Monitoring Kubernetes, VictoriaMetrics, Sensu, LogicMonitor, Distributed tracing, Datadog Monitors
- Architecture, Event-driven architecture (EDA), Service-oriented architecture (SOA), TOGAF, AWS Certified Solutions Architect-Associate (SSA), AWS Well-Architected Framework, SAFe Architect (ARCH), Open CA, SDLC, LLD, HLD, Architectural pattern, ODS, Archimate, Best practices, Good practices
Advertising:
