Commit a1f2fb58 authored by Michele Tartara's avatar Michele Tartara
Browse files

Add design for LV data collector

Add a section describing the logical volume data collector to the design
document for the monitoring agent.
Signed-off-by: default avatarMichele Tartara <>
Reviewed-by: default avatarHelga Velroyen <>
parent fae96b7c
......@@ -391,6 +391,82 @@ the following fields:
this field. This can provide an easy measure of both I/O completion time
and the backlog that may be accumulating.
Logical Volume collector
This data collector will gather information about the attributes of logical
volumes present in the system.
Its ``kind`` in the report will be ``0`` (`Performance reporting collectors`_).
Its ``category`` field in the report will contain the value ``storage``.
The ``data`` section of the report of this collector will be a list of items,
each representing one logical volume and providing the following fields:
The UUID of the logical volume.
The name of the logical volume.
The attributes of the logical volume.
Persistent major number or -1 if not persistent.
Persistent minor number or -1 if not persistent.
Currently assigned major number or -1 if LV is not active.
Currently assigned minor number or -1 if LV is not active.
Size of LV in bytes.
Number of segments in LV.
Tags, if any.
Kernel device-mapper modules required for this LV, if any.
Unique identifier of the volume group.
Name of the volume group.
Type of LV segment.
Offset within the LVto the start of the segment in bytes.
Offset within the LV to the start of the segment in physical extents.
Size of the segment in bytes.
Tags for the segment, if any.
Ranges of Physical Extents of underlying devices in lvs command line format.
Underlying devices used with starting extent numbers.
The name of the instance this LV is used by.
DRBD status
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment