Revision fae96b7c
| b/doc/design-monitoring-agent.rst | ||
|---|---|---|
| 315 | 315 |
Each ``storage`` collector's ``data`` section will provide collector-specific |
| 316 | 316 |
fields. |
| 317 | 317 |
|
| 318 |
In case of error, the ``message`` subfield of the ``status`` field of the |
|
| 319 |
report of the instance status collector will disclose the nature of the error |
|
| 320 |
as a type specific information. Examples of these are "backend pv unavailable" |
|
| 321 |
for lvm storage, "unreachable" for network based storage or "filesystem error" |
|
| 322 |
for filesystem based implementations. |
|
| 318 |
The various storage collectors will provide keys to join the data they provide, |
|
| 319 |
in order to allow the user to get a better understanding of the system. E.g.: |
|
| 320 |
through device names, or instance names. |
|
| 323 | 321 |
|
| 324 | 322 |
Diskstats collector |
| 325 | 323 |
******************* |
| ... | ... | |
| 374 | 372 |
This is the total number of sectors written successfully. |
| 375 | 373 |
|
| 376 | 374 |
``timeWrite`` |
| 377 |
This is the total number of milliseconds spent by all writes |
|
| 375 |
This is the total number of milliseconds spent by all writes.
|
|
| 378 | 376 |
|
| 379 | 377 |
``ios`` |
| 380 | 378 |
The number of I/Os currently in progress. |
Also available in: Unified diff