| 1 | <!--startmeta |
| 2 | custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/collectors/proc.plugin/integrations/system_uptime.md" |
| 3 | meta_yaml: "https://github.com/netdata/netdata/edit/master/src/collectors/proc.plugin/metadata.yaml" |
| 4 | sidebar_label: "System Uptime" |
| 5 | learn_status: "Published" |
| 6 | learn_rel_path: "Collecting Metrics/Collectors/Operating Systems" |
| 7 | keywords: ['uptime'] |
| 8 | message: "DO NOT EDIT THIS FILE DIRECTLY, IT IS GENERATED BY THE COLLECTOR'S metadata.yaml FILE" |
| 9 | endmeta--> |
| 10 | |
| 11 | # System Uptime |
| 12 | |
| 13 | |
| 14 | <img src="https://netdata.cloud/img/linuxserver.svg" width="150"/> |
| 15 | |
| 16 | |
| 17 | Plugin: proc.plugin |
| 18 | Module: /proc/uptime |
| 19 | |
| 20 | <img src="https://img.shields.io/badge/maintained%20by-Netdata-%2300ab44" /> |
| 21 | |
| 22 | ## Overview |
| 23 | |
| 24 | The amount of time the system has been up (running). |
| 25 | |
| 26 | Uptime is a critical aspect of overall system performance: |
| 27 | |
| 28 | - **Availability**: Uptime monitoring can show whether a server is consistently available or experiences frequent downtimes. |
| 29 | - **Performance Monitoring**: While server uptime alone doesn't provide detailed performance data, analyzing the duration and frequency of downtimes can help identify patterns or trends. |
| 30 | - **Proactive problem detection**: If server uptime monitoring reveals unexpected downtimes or a decreasing uptime trend, it can serve as an early warning sign of potential problems. |
| 31 | - **Root cause analysis**: When investigating server downtime, the uptime metric alone may not provide enough information to pinpoint the exact cause. |
| 32 | - **Load balancing**: Uptime data can indirectly indicate load balancing issues if certain servers have significantly lower uptimes than others. |
| 33 | - **Optimize maintenance efforts**: Servers with consistently low uptimes or frequent downtimes may require more attention. |
| 34 | - **Compliance requirements**: Server uptime data can be used to demonstrate compliance with regulatory requirements or SLAs that mandate a minimum level of server availability. |
| 35 | |
| 36 | |
| 37 | |
| 38 | |
| 39 | This collector is only supported on the following platforms: |
| 40 | |
| 41 | - linux |
| 42 | |
| 43 | This collector only supports collecting metrics from a single instance of this integration. |
| 44 | |
| 45 | |
| 46 | ### Default Behavior |
| 47 | |
| 48 | #### Auto-Detection |
| 49 | |
| 50 | This integration doesn't support auto-detection. |
| 51 | |
| 52 | #### Limits |
| 53 | |
| 54 | The default configuration for this integration does not impose any limits on data collection. |
| 55 | |
| 56 | #### Performance Impact |
| 57 | |
| 58 | The default configuration for this integration is not expected to impose a significant performance impact on the system. |
| 59 | |
| 60 | ## Setup |
| 61 | |
| 62 | |
| 63 | ### Prerequisites |
| 64 | |
| 65 | No action required. |
| 66 | |
| 67 | ### Configuration |
| 68 | |
| 69 | #### Options |
| 70 | |
| 71 | |
| 72 | |
| 73 | There are no configuration options. |
| 74 | |
| 75 | |
| 76 | |
| 77 | #### via File |
| 78 | |
| 79 | There is no configuration file. |
| 80 | |
| 81 | ##### Examples |
| 82 | There are no configuration examples. |
| 83 | |
| 84 | |
| 85 | |
| 86 | ## Alerts |
| 87 | |
| 88 | There are no alerts configured by default for this integration. |
| 89 | |
| 90 | |
| 91 | ## Metrics |
| 92 | |
| 93 | Metrics grouped by *scope*. |
| 94 | |
| 95 | The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels. |
| 96 | |
| 97 | |
| 98 | |
| 99 | ### Per System Uptime instance |
| 100 | |
| 101 | |
| 102 | |
| 103 | This scope has no labels. |
| 104 | |
| 105 | Metrics: |
| 106 | |
| 107 | | Metric | Dimensions | Unit | |
| 108 | |:------|:----------|:----| |
| 109 | | system.uptime | uptime | seconds | |
| 110 | |
| 111 |