-
Feature Request
-
Resolution: Unresolved
-
Undefined
-
None
-
None
-
False
-
None
-
False
-
Not Selected
-
-
-
What is the nature and description of the request?
As a telco customer, process of collecting all the data may need several iterations and I would like to reduce this by simply asking for 'all the data' .
Why does the customer need this? (List the business requirements here)
(mostly) Telco customers (working mostly in disconnected settings), can't always access clusters easily (they may be at remote locations, or isolated for various needs).
This makes it tedious/painful to access the cluster multiple times to collect data, thus an effort to minimize the number of times an admin has to access to cluster is desired. Hence the request for an option to collect as much data as possible in a single iteration.
While this is already possible with must-gather by specifying multiple images, admins/users don't always remember to do this. Thus being able to intuit what collector images should be run on a cluster (from this list https://docs.openshift.com/container-platform/4.13/support/gathering-cluster-data.html#gathering-data-specific-features_gathering-cluster-data) based on what is running on the cluster; ultimately minimizing cognitive load on users needing to specify which images they want to collect data on; and ensuring the 'right' (or as right as we can guess) data is collected for a case, is key to delivering a better customer experience.
List any affected packages or components.
oc
[RFE-3683] must-gather introspect of cluster components to select collection image that are run
| Component/s | New: must-gather [ 12404977 ] |
| Workflow | Original: Software Simplified Workflow for Project RFE v1.0 [ 22804875 ] | New: RH1-WF-X [ 27054880 ] |
| Status | Original: Under Review [ 14442 ] | New: Refinement [ 15021 ] |
| Link | New: This issue account is impacted by CLIOT-470 [ CLIOT-470 ] |
| Link | Original: This issue account is impacted by CLIOT-468 [ CLIOT-468 ] |
| Link | New: This issue account is impacted by CLIOT-468 [ CLIOT-468 ] |
Esha Vig
made changes -
| Link | New: This issue account is impacted by CLIOT-278 [ CLIOT-278 ] |
| Link | New: This issue relates to CNF-5969 [ CNF-5969 ] |
| Description |
Original:
*What is the nature and description of the request?*
As a telco customer, process of collecting all the data may need several iterations and I would like to reduce this by simply asking for 'all the data' . *Why does the customer need this? (List the business requirements here)* (mostly) Telco customers (working mostly in disconnected settings), can't always access clusters easily (they may be at remote locations, or isolated for various needs). This makes it tedious/painful to access the cluster multiple times to collect data, thus an effort to minimize the number of times an admin has to access to cluster is desired. Hence the request for an option to collect as much data as possible in a single iteration. While this is already possible with [must-gather|https://docs.openshift.com/container-platform/4.12/support/gathering-cluster-data.html#support_gathering_data_gathering-cluster-data] by specifying multiple images, admins/users don't always remember to do this. *List any affected packages or components.* oc |
New:
*What is the nature and description of the request?*
As a telco customer, process of collecting all the data may need several iterations and I would like to reduce this by simply asking for 'all the data' . *Why does the customer need this? (List the business requirements here)* (mostly) Telco customers (working mostly in disconnected settings), can't always access clusters easily (they may be at remote locations, or isolated for various needs). This makes it tedious/painful to access the cluster multiple times to collect data, thus an effort to minimize the number of times an admin has to access to cluster is desired. Hence the request for an option to collect as much data as possible in a single iteration. While this is already possible with [must-gather|https://docs.openshift.com/container-platform/4.12/support/gathering-cluster-data.html#support_gathering_data_gathering-cluster-data] by specifying multiple images, admins/users don't always remember to do this. Thus being able to intuit what collector images should be run on a cluster (from this list [https://docs.openshift.com/container-platform/4.13/support/gathering-cluster-data.html#gathering-data-specific-features_gathering-cluster-data)] based on what is running on the cluster; ultimately minimizing cognitive load on users needing to specify which images they want to collect data on; and ensuring the 'right' (or as right as we can guess) data is collected for a case, is key to delivering a better customer experience. *List any affected packages or components.* oc |
| Status | Original: Backlog [ 10824 ] | New: Under Review [ 14442 ] |
| Link | New: This issue is related to ECOPS-20 [ ECOPS-20 ] |
Bryan Litton
made changes -
| Assignee | Original: Robert Love [ rolove ] | New: Franck Baudin [ fbaudin@redhat.com ] |
| Assignee | Original: Gaurav Singh [ gausingh@redhat.com ] | New: Robert Love [ rolove ] |
| Contributors | New: Martin Sivak [ marsik ] |
| Link | New: This issue is related to PLM-618 [ PLM-618 ] |
| Labels | Original: sb_tracked | New: sb_tracked telco |
| Labels | New: sb_tracked |
| Remote Link | New: This issue links to "Slack conversation on the validity of the request (Web Link)" [ 1167329 ] |