master
md 138 lines 3.98 KB
Rendered Raw
1 <!--startmeta
2 custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/collectors/debugfs.plugin/integrations/power_capping.md"
3 meta_yaml: "https://github.com/netdata/netdata/edit/master/src/collectors/debugfs.plugin/metadata.yaml"
4 sidebar_label: "Power Capping"
5 learn_status: "Published"
6 learn_rel_path: "Collecting Metrics/Collectors/Hardware and Sensors"
7 keywords: ['power capping', 'energy']
8 message: "DO NOT EDIT THIS FILE DIRECTLY, IT IS GENERATED BY THE COLLECTOR'S metadata.yaml FILE"
9 endmeta-->
10
11 # Power Capping
12
13
14 <img src="https://netdata.cloud/img/powersupply.svg" width="150"/>
15
16
17 Plugin: debugfs.plugin
18 Module: intel_rapl
19
20 <img src="https://img.shields.io/badge/maintained%20by-Netdata-%2300ab44" />
21
22 ## Overview
23
24 Collects power capping performance metrics on Linux systems.
25
26
27 Parse data from `debugfs file.
28
29 This collector is only supported on the following platforms:
30
31 - Linux
32
33 This collector only supports collecting metrics from a single instance of this integration.
34
35 This integration requires read access to files under `/sys/devices/virtual/powercap`, which are accessible only to the root user by default. Netdata uses Linux Capabilities to give the plugin access to debugfs. `CAP_DAC_READ_SEARCH` is added automatically during installation. This capability allows bypassing file read permission checks and directory read and execute permission checks. If file capabilities are not usable, then the plugin is instead installed with the SUID bit set in permissions so that it runs as root.
36
37
38 ### Default Behavior
39
40 #### Auto-Detection
41
42 Assuming that debugfs is mounted and the required permissions are available, this integration will automatically detect whether or not the system is using zswap.
43
44
45 #### Limits
46
47 The default configuration for this integration does not impose any limits on data collection.
48
49 #### Performance Impact
50
51 The default configuration for this integration is not expected to impose a significant performance impact on the system.
52
53 ## Setup
54
55
56 ### Prerequisites
57
58 #### filesystem
59
60 The debugfs filesystem must be mounted on your host for plugin to collect data. You can run the command-line (`sudo mount -t debugfs none /sys/kernel/debug/`) to mount it locally. It is also recommended to modify your fstab (5) avoiding necessity to mount the filesystem before starting netdata.
61
62
63
64 ### Configuration
65
66 #### Options
67
68
69
70 <details open><summary>Config options</summary>
71
72
73
74 | Option | Description | Default | Required |
75 |:-----|:------------|:--------|:---------:|
76 | update every | Data collection frequency. | 1 | no |
77 | command options | Additinal parameters for collector | | no |
78
79
80 </details>
81
82
83
84 #### via File
85
86 The configuration file name for this integration is `netdata.conf`.
87 Configuration for this specific integration is located in the `[plugin:debugfs]` section within that file.
88
89 The file format is a modified INI syntax. The general structure is:
90
91 ```ini
92 [section1]
93 option1 = some value
94 option2 = some other value
95
96 [section2]
97 option3 = some third value
98 ```
99 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-configuration-files) script from the
100 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#locate-your-config-directory).
101
102 ```bash
103 cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
104 sudo ./edit-config netdata.conf
105 ```
106
107 ##### Examples
108 There are no configuration examples.
109
110
111
112 ## Alerts
113
114 There are no alerts configured by default for this integration.
115
116
117 ## Metrics
118
119 Metrics grouped by *scope*.
120
121 The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
122
123 Monitor the Intel RAPL zones Consumption.
124
125 ### Per Power Capping instance
126
127 Global Intel RAPL zones.
128
129 This scope has no labels.
130
131 Metrics:
132
133 | Metric | Dimensions | Unit |
134 |:------|:----------|:----|
135 | cpu.powercap_intel_rapl_zone | Power | Watts |
136 | cpu.powercap_intel_rapl_subzones | dram, core, uncore | Watts |
137
138