常用告警规则

最新推荐文章于 2024-07-11 15:29:37 发布
最新推荐文章于 2024-07-11 15:29:37 发布
阅读量396 收藏 5
点赞数 3
文章标签： 前端 java
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/qq_36810403/article/details/139786624
版权

Node_exporter告警规则
NodeCPUUsageHigh:

yaml
复制代码

  • alert: NodeCPUUsageHigh
    expr: (100 - (avg by (instance) (rate(node_cpu_seconds_total{mode=“idle”}[5m])) * 100)) > 80
    for: 5m
    labels:
    severity: critical
    annotations:
    summary: “High CPU usage detected on {{ $labels.instance }}”
    description: “CPU usage is above 80% for more than 5 minutes on {{ $labels.instance }}.”
    解释：当某节点的CPU使用率超过80%并持续5分钟时触发告警。

NodeMemoryUsageHigh:

yaml
复制代码

  • alert: NodeMemoryUsageHigh
    expr: (node_memory_MemTotal_bytes - node_memory_MemAvailable_bytes) / node_memory_MemTotal_bytes * 100 > 90
    for: 5m
    labels:
    severity: critical
    annotations:
    summary: “High Memory usage detected on {{ $labels.instance }}”
    description: “Memory usage is above 90% for more than 5 minutes on {{ $labels.instance }}.”
    解释：当某节点的内存使用率超过90%并持续5分钟时触发告警。

NodeDiskUsageHigh:

yaml
复制代码

  • alert: NodeDiskUsageHigh
    expr: (node_filesystem_size_bytes{fstype!~“tmpfs|fuse.lxcfs”} - node_filesystem_free_bytes{fstype!~“tmpfs|fuse.lxcfs”}) / node_filesystem_size_bytes{fstype!~“tmpfs|fuse.lxcfs”} * 100 > 85
    for: 5m
    labels:
    severity: warning
    annotations:
    summary: “High Disk usage detected on {{ $labels.instance }}”
    description: “Disk usage is above 85% for more than 5 minutes on {{ $labels.instance }}.”
    解释：当某节点的磁盘使用率超过85%并持续5分钟时触发告警。

NodeFilesystemReadOnly:

yaml
复制代码

  • alert: NodeFilesystemReadOnly
    expr: node_filesystem_readonly{fstype!~“tmpfs|fuse.lxcfs”} == 1
    for: 10m
    labels:
    severity: critical
    annotations:
    summary: “Filesystem is read-only on {{ $labels.instance }}”
    description: “Filesystem has been read-only for more than 10 minutes on {{ $labels.instance }}.”
    解释：当某节点的文件系统变为只读并持续10分钟时触发告警。

NodeLoadAverageHigh:

yaml
复制代码

  • alert: NodeLoadAverageHigh
    expr: node_load1 > 2 * count(node_cpu_seconds_total{mode=“system”})
    for: 5m
    labels:
    severity: warning
    annotations:
    summary: “High load average on {{ $labels.instance }}”
    description: “1-minute load average is more than twice the number of CPUs for over 5 minutes on {{ $labels.instance }}.”
    解释：当某节点的1分钟负载平均值超过CPU数量的2倍并持续5分钟时触发告警。

NodeNetworkDown:

yaml
复制代码

  • alert: NodeNetworkDown
    expr: up{job=“node_exporter”} == 0
    for: 10m
    labels:
    severity: critical
    annotations:
    summary: “Node down: {{ $labels.instance }}”
    description: “Node has been down for more than 10 minutes.”
    解释：当某节点的node_exporter数据10分钟内没有上报时触发告警。

NodeSwapUsageHigh:

yaml
复制代码

  • alert: NodeSwapUsageHigh
    expr: (node_memory_SwapTotal_bytes - node_memory_SwapFree_bytes) / node_memory_SwapTotal_bytes * 100 > 50
    for: 5m
    labels:
    severity: warning
    annotations:
    summary: “High swap usage on {{ $labels.instance }}”
    description: “Swap usage is above 50% for more than 5 minutes on {{ $labels.instance }}.”
    解释：当某节点的交换分区使用率超过50%并持续5分钟时触发告警。

NodeFileSystemInodesUsageHigh:

yaml
复制代码

  • alert: NodeFileSystemInodesUsageHigh
    expr: (node_filesystem_files - node_filesystem_files_free) / node_filesystem_files * 100 > 80
    for: 5m
    labels:
    severity: warning
    annotations:
    summary: “High filesystem inodes usage on {{ $labels.instance }}”
    description: “Filesystem inodes usage is above 80% for more than 5 minutes on {{ $labels.instance }}.”
    解释：当某节点的文件系统inode使用率超过80%并持续5分钟时触发告警。

NodeTemperatureHigh:

yaml
复制代码

  • alert: NodeTemperatureHigh
    expr: node_hwmon_temp_celsius > 75
    for: 5m
    labels:
    severity: warning
    annotations:
    summary: “High temperature on {{ $labels.instance }}”
    description: “Node temperature is above 75 degrees Celsius for more than 5 minutes on {{ $labels.instance }}.”
    解释：当某节点的温度超过75摄氏度并持续5分钟时触发告警。

NodeProcessCountHigh:

yaml
复制代码

  • alert: NodeProcessCountHigh
    expr: count(node_scrape_collector_duration_seconds) > 500
    for: 5m
    labels:
    severity: warning
    annotations:
    summary: “High process count on {{ $labels.instance }}”
    description: “Number of processes is above 500 for more than 5 minutes on {{ $labels.instance }}.”
    解释：当某节点的进程数超过500并持续5分钟时触发告警。

windows_exporter告警规则
WindowsCPUUsageHigh:

yaml
复制代码

  • alert: WindowsCPUUsageHigh
    expr: avg by (instance) (rate(windows_cpu_time_total{mode=“idle”}[5m])) < 0.2
    for: 5m
    labels:
    severity: critical
    annotations:
    summary: “High CPU usage on {{ $labels.instance }}”
    description: “CPU usage is above 80% for more than 5 minutes on {{ $labels.instance }}.”
    解释：当某Windows节点的CPU使用率超过80%并持续5分钟时触发告警。

WindowsMemoryUsageHigh:

yaml
复制代码

  • alert: WindowsMemoryUsageHigh
    expr: windows_cs_physical_memory_bytes - windows_os_physical_memory_free_bytes / windows_cs_physical_memory_bytes * 100 > 90
    for: 5m
    labels:
    severity: critical
    annotations:
    summary: “High Memory usage on {{ $labels.instance }}”
    description: “Memory usage is above 90% for more than 5 minutes on {{ $labels.instance }}.”
    解释：当某Windows节点的内存使用率超过90%并持续5分钟时触发告警。

WindowsDiskUsageHigh:

yaml
复制代码

  • alert: WindowsDiskUsageHigh
    expr: windows_logical_disk_free_bytes / windows_logical_disk_size_bytes * 100 < 15
    for: 5m
    labels:
    severity: warning
    annotations:
    summary: “High Disk usage on {{ $labels.instance }}”
    description: “Disk usage is above 85% for more than 5 minutes on {{ $labels.instance }}.”
    解释：当某Windows节点的磁盘使用率超过85%并持续5分钟时触发告警。

WindowsNetworkDown:

yaml
复制代码

  • alert: WindowsNetworkDown
    expr: up{job=“windows_exporter”} == 0
    for: 10m
    labels:
    severity: critical
    annotations:
    summary: “Node down: {{ $labels.instance }}”
    description: “Node has been down for more than 10 minutes.”
    解释：当某Windows节点的windows_exporter数据10分钟内没有上报时触发告警。

WindowsServiceNotRunning:

yaml
复制代码

  • alert: WindowsServiceNotRunning
    expr: windows_service_status == 2
    for: 5m
    labels:
    severity: critical
    annotations:
    summary: “Service not running on {{ $labels.instance }}”
    description: “A critical service is not running for more than 5 minutes on {{ $labels.instance }}.”
    解释：当某Windows节点上的某关键服务未运行并持续5分钟时触发告警。

WindowsPageFileUsageHigh:

yaml
复制代码

  • alert: WindowsPageFileUsageHigh
    expr: windows_os_paging_free_bytes / windows_os_paging_limit_bytes * 100
    继续

ChatGPT
windows_exporter告警规则（续）
WindowsPageFileUsageHigh:

yaml
复制代码

  • alert: WindowsPageFileUsageHigh
    expr: windows_os_paging_free_bytes / windows_os_paging_limit_bytes * 100 < 10
    for: 5m
    labels:
    severity: warning
    annotations:
    summary: “High Page File usage on {{ $labels.instance }}”
    description: “Page file usage is above 90% for more than 5 minutes on {{ $labels.instance }}.”
    解释：当某Windows节点的页面文件使用率超过90%并持续5分钟时触发告警。

WindowsHandleCountHigh:

yaml
复制代码

  • alert: WindowsHandleCountHigh
    expr: windows_process_handles_count > 10000
    for: 5m
    labels:
    severity: warning
    annotations:
    summary: “High Handle count on {{ $labels.instance }}”
    description: “Number of handles is above 10,000 for more than 5 minutes on {{ $labels.instance }}.”
    解释：当某Windows节点的句柄数超过10,000并持续5分钟时触发告警。

WindowsThreadCountHigh:

yaml
复制代码

  • alert: WindowsThreadCountHigh
    expr: windows_process_threads > 500
    for: 5m
    labels:
    severity: warning
    annotations:
    summary: “High Thread count on {{ $labels.instance }}”
    description: “Number of threads is above 500 for more than 5 minutes on {{ $labels.instance }}.”
    解释：当某Windows节点的线程数超过500并持续5分钟时触发告警。

WindowsProcessorQueueLengthHigh:

yaml
复制代码

  • alert: WindowsProcessorQueueLengthHigh
    expr: windows_system_processor_queue_length > 10
    for: 5m
    labels:
    severity: warning
    annotations:
    summary: “High Processor Queue Length on {{ $labels.instance }}”
    description: “Processor queue length is above 10 for more than 5 minutes on {{ $labels.instance }}.”
    解释：当某Windows节点的处理器队列长度超过10并持续5分钟时触发告警。

WindowsDiskIOWaitHigh:

yaml
复制代码

  • alert: WindowsDiskIOWaitHigh
    expr: avg by (instance) (rate(windows_logical_disk_idle_time{instance=~“[^:]+:.*”}[5m])) < 0.1
    for: 5m
    labels:
    severity: warning
    annotations:
    summary: “High Disk I/O Wait on {{ $labels.instance }}”
    description: “Disk I/O wait time is high for more than 5 minutes on {{ $labels.instance }}.”
    解释：当某Windows节点的磁盘I/O等待时间过高并持续5分钟时触发告警。

mysqld_exporter告警规则
MySQLHighThreadsRunning:

yaml
复制代码

  • alert: MySQLHighThreadsRunning
    expr: mysql_global_status_threads_running > 50
    for: 5m
    labels:
    severity: critical
    annotations:
    summary: “High number of running threads in MySQL on {{ $labels.instance }}”
    description: “Number of running threads is above 50 for more than 5 minutes on {{ $labels.instance }}.”
    解释：当MySQL实例的运行线程数超过50并持续5分钟时触发告警。

MySQLSlowQueries:

yaml
复制代码

  • alert: MySQLSlowQueries
    expr: rate(mysql_global_status_slow_queries[5m]) > 0
    for: 10m
    labels:
    severity: warning
    annotations:
    summary: “Slow queries detected on {{ $labels.instance }}”
    description: “One or more slow queries detected in the last 10 minutes on {{ $labels.instance }}.”
    解释：当MySQL实例在过去10分钟内检测到慢查询时触发告警。

MySQLReplicationLag:

yaml
复制代码

  • alert: MySQLReplicationLag
    expr: mysql_slave_status_seconds_behind_master > 10
    for: 5m
    labels:
    severity: critical
    annotations:
    summary: “Replication lag on MySQL slave {{ $labels.instance }}”
    description: “Replication lag is more than 10 seconds for over 5 minutes on {{ $labels.instance }}.”
    解释：当MySQL从库的复制延迟超过10秒并持续5分钟时触发告警。

MySQLHighConnections:

yaml
复制代码

  • alert: MySQLHighConnections
    expr: mysql_global_status_threads_connected > 200
    for: 5m
    labels:
    severity: critical
    annotations:
    summary: “High number of connections to MySQL on {{ $labels.instance }}”
    description: “Number of connections is above 200 for more than 5 minutes on {{ $labels.instance }}.”
    解释：当MySQL实例的连接数超过200并持续5分钟时触发告警。

MySQLLowFreeDiskSpace:

yaml
复制代码

  • alert: MySQLLowFreeDiskSpace
    expr: (mysql_global_variables_datadir - node_filesystem_free_bytes{fstype!~“tmpfs|fuse.lxcfs”}) / mysql_global_variables_datadir * 100 > 90
    for: 10m
    labels:
    severity: critical
    annotations:
    summary: “Low free disk space for MySQL on {{ $labels.instance }}”
    description: “Free disk space for MySQL data directory is below 10% for more than 10 minutes on {{ $labels.instance }}.”
    解释：当MySQL实例的数据目录剩余磁盘空间低于10%并持续10分钟时触发告警。

MySQLHighQueryTime:

yaml
复制代码

  • alert: MySQLHighQueryTime
    expr: rate(mysql_global_status_questions[5m]) > 1000
    for: 5m
    labels:
    severity: warning
    annotations:
    summary: “High query rate on MySQL on {{ $labels.instance }}”
    description: “Query rate is above 1000 queries per second for more than 5 minutes on {{ $labels.instance }}.”
    解释：当MySQL实例的查询率超过每秒1000个并持续5分钟时触发告警。

MySQLInnoDBBufferPoolUsageHigh:

yaml
复制代码

  • alert: MySQLInnoDBBufferPoolUsageHigh
    expr: (mysql_global_status_innodb_buffer_pool_bytes_data / mysql_global_status_innodb_buffer_pool_bytes_total) * 100 > 85
    for: 5m
    labels:
    severity: warning
    annotations:
    summary: “High InnoDB buffer pool usage on MySQL on {{ $labels.instance }}”
    description: “InnoDB buffer pool usage is above 85% for more than 5 minutes on {{ $labels.instance }}.”
    解释：当MySQL实例的InnoDB缓冲池使用率超过85%并持续5分钟时触发告警。

MySQLMaxConnectionsReached:

yaml
复制代码

  • alert: MySQLMaxConnectionsReached
    expr: mysql_global_status_threads_connected / mysql_global_variables_max_connections * 100 > 90
    for: 5m
    labels:
    severity: critical
    annotations:
    summary: “Max connections threshold reached on MySQL on {{ $labels.instance }}”
    description: “Connections usage is above 90% of the max_connections limit for more than 5 minutes on {{ $labels.instance }}.”
    解释：当MySQL实例的连接数达到最大连接数限制的90%以上并持续5分钟时触发告警。

MySQLTableLocksContention:

yaml
复制代码

  • alert: MySQLTableLocksContention
    expr: rate(mysql_global_status_table_locks_waited[5m]) > 10
    for: 5m
    labels:
    severity: warning
    annotations:
    summary: “Table locks contention in MySQL on {{ $labels.instance }}”
    description: “More than 10 table locks waited per second for more than 5 minutes on {{ $labels.instance }}.”
    解释：当MySQL实例的表锁等待数超过每秒10个并持续5分钟时触发告警。

MySQLLongRunningQueries:

yaml
复制代码

  • alert: MySQLLongRunningQueries
    expr: mysql_global_status_queries{job=“mysql”} > 100
    for: 10m
    labels:
    severity: warning
    annotations:
    summary: “Long running queries in MySQL on {{ $labels.instance }}”
    description: “More than 100 long running queries for over 10 minutes on {{ $labels.instance }}.”
    解释：当MySQL实例的长时间运行查询超过100个并持续10分钟时触发告警。

blackbox_exporter告警规则
EndpointDown:
yaml
复制代码

  • alert: EndpointDown
    expr: probe_success == 0
    for:
    继续

ChatGPT
blackbox_exporter告警规则
EndpointDown:

yaml
复制代码

  • alert: EndpointDown
    expr: probe_success == 0
    for: 5m
    labels:
    severity: critical
    annotations:
    summary: “Endpoint down: {{ $labels.instance }}”
    description: “The endpoint {{ $labels.instance }} has been down for more than 5 minutes.”
    解释：当某个端点连续5分钟探测失败时触发告警。

EndpointHighLatency:

yaml
复制代码

  • alert: EndpointHighLatency
    expr: probe_duration_seconds > 0.5
    for: 5m
    labels:
    severity: warning
    annotations:
    summary: “High latency on endpoint: {{ $labels.instance }}”
    description: “The endpoint {{ $labels.instance }} has a latency higher than 0.5 seconds for more than 5 minutes.”
    解释：当某个端点的响应时间超过0.5秒并持续5分钟时触发告警。

EndpointDNSResolutionFailure:

yaml
复制代码

  • alert: EndpointDNSResolutionFailure
    expr: probe_dns_lookup_time_seconds > 2
    for: 5m
    labels:
    severity: warning
    annotations:
    summary: “DNS resolution failure for endpoint: {{ $labels.instance }}”
    description: “The endpoint {{ $labels.instance }} has DNS resolution time higher than 2 seconds for more than 5 minutes.”
    解释：当某个端点的DNS解析时间超过2秒并持续5分钟时触发告警。

EndpointConnectionTimeout:

yaml
复制代码

  • alert: EndpointConnectionTimeout
    expr: probe_tcp_connect_duration_seconds > 1
    for: 5m
    labels:
    severity: warning
    annotations:
    summary: “Connection timeout on endpoint: {{ $labels.instance }}”
    description: “The endpoint {{ $labels.instance }} has connection timeout higher than 1 second for more than 5 minutes.”
    解释：当某个端点的连接时间超过1秒并持续5分钟时触发告警。

EndpointCertificateExpiry:

yaml
复制代码

  • alert: EndpointCertificateExpiry
    expr: probe_ssl_earliest_cert_expiry - time() < 86400 * 7
    for: 1h
    labels:
    severity: warning
    annotations:
    summary: “SSL certificate expiry for endpoint: {{ $labels.instance }}”
    description: “The SSL certificate for endpoint {{ $labels.instance }} will expire in less than 7 days.”
    解释：当某个端点的SSL证书将在7天内过期时触发告警。

HTTPResponseCodeMismatch:

yaml
复制代码

  • alert: HTTPResponseCodeMismatch
    expr: probe_http_status_code != 200
    for: 5m
    labels:
    severity: warning
    annotations:
    summary: “Unexpected HTTP response code on endpoint: {{ $labels.instance }}”
    description: “The endpoint {{ $labels.instance }} returned an unexpected HTTP response code for more than 5 minutes.”
    解释：当某个端点的HTTP响应码不是200并持续5分钟时触发告警。

EndpointHTTPRedirects:

yaml
复制代码

  • alert: EndpointHTTPRedirects
    expr: probe_http_redirects > 5
    for: 5m
    labels:
    severity: warning
    annotations:
    summary: “Too many HTTP redirects on endpoint: {{ $labels.instance }}”
    description: “The endpoint {{ $labels.instance }} encountered more than 5 HTTP redirects for more than 5 minutes.”
    解释：当某个端点的HTTP重定向次数超过5次并持续5分钟时触发告警。

EndpointDNSLookupFailures:

yaml
复制代码

  • alert: EndpointDNSLookupFailures
    expr: increase(probe_dns_lookup_time_seconds[5m]) > 0
    for: 10m
    labels:
    severity: warning
    annotations:
    summary: “DNS lookup failures on endpoint: {{ $labels.instance }}”
    description: “The endpoint {{ $labels.instance }} had DNS lookup failures for more than 10 minutes.”
    解释：当某个端点在10分钟内有DNS解析失败时触发告警。

EndpointTCPConnectionRefused:

yaml
复制代码

  • alert: EndpointTCPConnectionRefused
    expr: probe_tcp_connect_success == 0
    for: 5m
    labels:
    severity: critical
    annotations:
    summary: “TCP connection refused on endpoint: {{ $labels.instance }}”
    description: “The endpoint {{ $labels.instance }} refused TCP connections for more than 5 minutes.”
    解释：当某个端点连续5分钟TCP连接失败时触发告警。

EndpointSSLCertificateInvalid:

yaml
复制代码

  • alert: EndpointSSLCertificateInvalid
    expr: probe_ssl_last_chain_expiry_timestamp_seconds - time() < 0
    for: 5m
    labels:
    severity: critical
    annotations:
    summary: “Invalid SSL certificate on endpoint: {{ $labels.instance }}”
    description: “The endpoint {{ $labels.instance }} has an invalid SSL certificate.”
    解释：当某个端点的SSL证书无效时触发告警。

cAdvisor告警规则
ContainerCPUUsageHigh:

yaml
复制代码

  • alert: ContainerCPUUsageHigh
    expr: rate(container_cpu_usage_seconds_total[5m]) > 0.8
    for: 5m
    labels:
    severity: warning
    annotations:
    summary: “High CPU usage on container {{ $labels.container }}”
    description: “Container {{ $labels.container }} has CPU usage above 80% for more than 5 minutes.”
    解释：当某个容器的CPU使用率超过80%并持续5分钟时触发告警。

ContainerMemoryUsageHigh:

yaml
复制代码

  • alert: ContainerMemoryUsageHigh
    expr: container_memory_usage_bytes / container_spec_memory_limit_bytes > 0.9
    for: 5m
    labels:
    severity: critical
    annotations:
    summary: “High memory usage on container {{ $labels.container }}”
    description: “Container {{ $labels.container }} has memory usage above 90% for more than 5 minutes.”
    解释：当某个容器的内存使用率超过90%并持续5分钟时触发告警。

ContainerDiskIOHigh:

yaml
复制代码

  • alert: ContainerDiskIOHigh
    expr: rate(container_fs_io_time_seconds_total[5m]) > 0.5
    for: 5m
    labels:
    severity: warning
    annotations:
    summary: “High disk I/O on container {{ $labels.container }}”
    description: “Container {{ $labels.container }} has disk I/O usage above 50% for more than 5 minutes.”
    解释：当某个容器的磁盘I/O使用率超过50%并持续5分钟时触发告警。

ContainerNetworkErrors:

yaml
复制代码

  • alert: ContainerNetworkErrors
    expr: rate(container_network_receive_errors_total[5m]) > 0 or rate(container_network_transmit_errors_total[5m]) > 0
    for: 5m
    labels:
    severity: warning
    annotations:
    summary: “Network errors on container {{ $labels.container }}”
    description: “Container {{ $labels.container }} is experiencing network errors for more than 5 minutes.”
    解释：当某个容器在5分钟内出现网络错误时触发告警。

ContainerRestarting:

yaml
复制代码

  • alert: ContainerRestarting
    expr: rate(container_restart_count[5m]) > 1
    for: 5m
    labels:
    severity: critical
    annotations:
    summary: “Container restarting frequently: {{ $labels.container }}”
    description: “Container {{ $labels.container }} has restarted more than once in the last 5 minutes.”
    解释：当某个容器在5分钟内重启超过1次时触发告警。

ContainerOOMKilled:

yaml
复制代码

  • alert: ContainerOOMKilled
    expr: container_last_seen < time() - 300 and container_state_terminated_reason == “OOMKilled”
    for: 5m
    labels:
    severity: critical
    annotations:
    summary: “Container OOMKilled: {{ $labels.container }}”
    description: “Container {{ $labels.container }} was killed due to out of memory in the last 5 minutes.”
    解释：当某个容器在过去5分钟内因内存不足被杀死时触发告警。

ContainerFileSystemFull:

yaml
复制代码

  • alert: ContainerFileSystemFull
    expr: container_fs_usage_bytes / container_fs_limit_bytes > 0.9
    for: 5m
    labels:
    severity: critical
    annotations:
    summary: “File system full on container {{ $labels.container }}”
    description: "Container {{ $labels.container }} file system usage is above 90
    继续

ChatGPT
cAdvisor告警规则（续）
ContainerFileSystemFull:

yaml
复制代码

  • alert: ContainerFileSystemFull
    expr: container_fs_usage_bytes / container_fs_limit_bytes > 0.9
    for: 5m
    labels:
    severity: critical
    annotations:
    summary: “File system full on container {{ $labels.container }}”
    description: “Container {{ $labels.container }} file system usage is above 90% for more than 5 minutes.”
    解释：当某个容器的文件系统使用率超过90%并持续5分钟时触发告警。

ContainerMemoryLeak:

yaml
复制代码

  • alert: ContainerMemoryLeak
    expr: increase(container_memory_usage_bytes[1h]) > 1000000000
    for: 1h
    labels:
    severity: warning
    annotations:
    summary: “Possible memory leak on container {{ $labels.container }}”
    description: “Container {{ $labels.container }} has increased its memory usage by more than 1 GB in the last hour.”
    解释：当某个容器在过去1小时内内存使用量增加超过1GB时触发告警，可能存在内存泄漏。

ContainerHighCPUThrottling:

yaml
复制代码

  • alert: ContainerHighCPUThrottling
    expr: rate(container_cpu_cfs_throttled_seconds_total[5m]) / rate(container_cpu_cfs_periods_total[5m]) > 0.2
    for: 5m
    labels:
    severity: warning
    annotations:
    summary: “High CPU throttling on container {{ $labels.container }}”
    description: “Container {{ $labels.container }} is experiencing CPU throttling more than 20% of the time for more than 5 minutes.”
    解释：当某个容器在5分钟内CPU限制（throttling）时间超过总时间的20%时触发告警。

ContainerNetworkTrafficDrop:

yaml
复制代码

  • alert: ContainerNetworkTrafficDrop
    expr: rate(container_network_receive_packets_dropped_total[5m]) > 0 or rate(container_network_transmit_packets_dropped_total[5m]) > 0
    for: 5m
    labels:
    severity: warning
    annotations:
    summary: “Network traffic drops on container {{ $labels.container }}”
    description: “Container {{ $labels.container }} is experiencing network packet drops for more than 5 minutes.”
    解释：当某个容器在5分钟内出现网络数据包丢失时触发告警。

这些告警规则基于不同的exporter，可以帮助监控和管理系统和服务的健康状态。通过定义合适的阈值和条件，您可以及时发现和解决潜在问题，确保系统的稳定性和性能。

远洋z
关注
  • 3
    点赞
  • 踩
  • 5
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
【微服务】skywalking自定义告警规则使用详解
congge
02-15 5620
skywalking自定义告警规则使用详解
Prometheus基于kubernetes告警规则-告警等级划分（不同渠道告警）
weixin_43273856的博客
04-12 1671
Prometheus基于kubernetes告警规则-告警等级划分（不同渠道告警）
智能驱动｜ChatGPT视角下的告警事件闭环响应
2401_84466316的博客
06-04 1247
智能的工具可以极大的辅助安全从业人员在工作过程中高效处理问题，但是很多位置的思考还是不能完全自动智能化，需要人的参与才能完整进行。人是安全建设核心点，工具能解决重复且无需深度思考的繁重工作，当然机器人的智能是在大量算法和数据不断训练和优化中成长进化，智能机器人未来可期........网络安全学习资源分享:给大家分享一份全套的网络安全学习资料，给那些想学习 网络安全的小伙伴们一点帮助！对于从来没有接触过网络安全的同学，我们帮你准备了详细的学习成长路线图。
Prometheus常用告警规则
wangshui898的专栏
09-16 6471
Prometheus.rules cat > /data/prometheus/conf/rules/Prometheus.yaml << 'EOF' groups: - name: Prometheus.rules rules: - alert: PrometheusTargetMissing expr: up == 0 for: 0m labels: severity: critical annotations: summ
三、Prometheus常用告警规则rules.yml
SpringLei
08-16 9897
Prometheus常用服务告警规则rules.yml。
prometheus监控常用告警规则
qq_42890862的博客
01-13 4262
1、监控服务器是否重启 - alert: CentosServiceRestart expr: time() - node_boot_time_seconds < 180 for: 2m labels: severity: warning annotations: summary: "Instance is restart" description: "Instance is restarted, uptime <3min"
prometheus告警规则管理
wanger5354的博客
09-09 1606
微型公众号：运维开发故事，作者：夏老师 什么是Rule Prometheus支持用户自定义Rule规则。 Rule分为两类，一类是Recording Rule，另一类是Alerting Rule。Recording Rule的主要目的是通过PromQL可以实时对Prometheus中采集到的样本数据进行查询，聚合以及其它各种运算操作。而在某些PromQL较为复杂且计算量较大时，直接使用PromQL可能会导致Prometheus响应超时的情况。这时需要一种能够类似于后台批处理的机制能够在后台完成这些复杂运.
【Prometheus】Prometheus告警规则配置
superone52033的博客
03-21 1576
【prometheus】prometheus告警规则配置
常用prometheus告警规则模板
IT- 研究者
07-28 4733
应用类相关 1.监控应用是否可用 规则模板 : up=${value} 规则描述: 监测应用是否可用 参数说明: value:0表示宕机1表示可用 具体应用 groups: -name:example#报警规则组的名字 rules: -alert:InstanceDown#检测job的状态，持续1分钟metrices不能访问会发给altermanager进行报警 expr:up==0 for:1m#持续时...
prometheus监控mysql和报警规则详细资料—超详细，超全面(带文档和相关软件包)
06-04
本资料包提供了一套详尽的Prometheus监控MySQL以及设置报警规则的方法。 一、Prometheus监控MySQL原理 Prometheus通过其服务发现机制来找到MySQL实例，然后通过导出器（如`mysqld_exporter`）将MySQL的指标暴露出来...
SolarWinds常用告警，中文
05-27
在“SolarWinds常用告警，中文”这个主题中，我们主要关注的是如何利用SolarWinds来设置和管理告警，以便在系统出现潜在问题时能够及时收到通知。这些告警配置是预设的，可以直接导入到11.5及以上版本的SolarWinds...
prometheus监控redis和报警规则详细资料—超级详细(带文档和软件包)
06-04
本资料包提供了Prometheus监控Redis的详细教程，包括部署文档和相关软件包，旨在帮助用户理解如何设置和使用Prometheus来监控Redis，并配置报警规则以及时发现并处理问题。 首先，你需要了解如何安装Prometheus。...
电力通信网告警分层过滤机制的设计
04-16
为了保证有效防止电力...基于现有告警关联分析方法的比较，探讨了如何采用数据挖掘技术获取告警关联规则，并在此基础上构建了告警过滤规则知识库，提出一种新的告警分层过滤模型。实验证明了告警过滤机制的实用效果。
server-status.rules
01-29
Prometheus组件alertmanager常用告警规则 有CPU使用率、cpu_load5、cpu_load15、内存使用率、swap使用率、iowait、磁盘分区使用率、文件打开句柄数（自定义metrics）
Node多版本管理器NVM安装使用
最新发布
GongWeiBuQi的博客
07-11 184
安装node很方便，只需要一条命令可以轻松切换node版本可以多版本node并存。
vue实现预览编辑ppt、word、pdf、excel、等功能的解决方案（内网-前端）
m0_68271787的博客
07-10 762
在Vue中实现预览和编辑PPT、Word、PDF、Excel等文件的功能，尤其是在内网环境下且主要侧重于前端，我们需要明确的是，直接在前端编辑这些格式的文件（特别是PPT和Word）是非常复杂且通常不推荐的，因为这些格式涉及复杂的布局和格式设置。然而，我们可以实现预览功能，并可能通过一些间接方式支持简单的编辑（如表格数据的修改）。下面我将分别给出预览PPT、Word、PDF、Excel文件的Vue组件示例代码，并简要说明如何可能实现简单的编辑功能。
Javafx利用fxml变换场景的小细节
2301_80311013的博客
07-09 871
在这个代码中，在JavaFX中，FXMLLoader是用来加载FXML文件并将其转换为Java对象（例如控制器类）的工具。当您使用FXMLLoaderFXMLLoader在整个过程中，FXMLLoader是使用JavaFX的后台线程（也称为JavaFX线程）来执行这些操作的，这是为了保持UI线程的响应性。这意味着在用户界面（UI）线程中，您不会看到任何阻塞，即使FXMLLoader正在执行耗时的操作。当FXMLLoader完成加载并调用load()方法时，它会返回一个Parent。
prometheus 监控elasticsearch 告警规则
08-25
- *1* *2* [三、Prometheus常用告警规则rules.yml](https://blog.csdn.net/yeqinghanwu/article/details/126367493)[target="_blank" data-report-click={"spm":"1018.2226.3001.9630","extra":{"utm_source":"vip_...

“相关推荐”对你有帮助么？

  • 非常没帮助
  • 没帮助
  • 一般
  • 有帮助
  • 非常有帮助
提交
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值