Bug 2043147 - [GSS][Doc] Duplicate rows in Table 2.1. Indicators for Multicloud Object Gateway
Summary: [GSS][Doc] Duplicate rows in Table 2.1. Indicators for Multicloud Object Gateway
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat OpenShift Data Foundation
Classification: Red Hat Storage
Component: documentation
Version: 4.9
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: ---
: ---
Assignee: Ashish Singh
QA Contact: Elad
Olive Lakra
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-01-20 17:31 UTC by Sonal
Modified: 2023-08-09 16:43 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-04-21 09:12:44 UTC
Embargoed:


Attachments (Terms of Use)

Description Sonal 2022-01-20 17:31:09 UTC
Describe the issue:

The first two and last two rows are duplicate in 'Table 2.1. Indicators for Multicloud Object Gateway'

---
Accounts

I/O operations

Displays read and write I/O operations for the top five consumers. The total reads and writes of all the consumers is displayed at the bottom. This information helps you monitor the throughput demand (IOPS) per application or account.

Accounts

Logical Used Capacity

Displays total logical usage of each account for the top five consumers. This helps you monitor the throughput demand per application or account.
---

Describe the task you were trying to accomplish:

Suggestions for improvement:
Remove the bottom two rows from the table.

Document URL:

https://access.redhat.com/documentation/en-us/red_hat_openshift_data_foundation/4.9/html-single/monitoring_openshift_data_foundation#metrics-in-object-storage-dashboard_rhodf

Chapter/Section Number and Title:

Section 2.2. Metrics in the Object dashboard

Table 2.1. Indicators for Multicloud Object Gateway

Product Version:

ODF 4.9

Environment Details:
Any

Any other versions of this document that also needs this update:
No

Additional information:
-


Note You need to log in before you can comment on or make changes to this bug.