Important Update: Cohesity Products Documentation
All Cohesity product documentation are now managed via the Cohesity Docs Portal: https://docs.cohesity.com/HomePage/Content/home.htm. Some documentation available here may not reflect the latest information or may no longer be accessible.
System Health Insights User Guide
- Introduction
- Getting Started
- Registering an Appliance
- Associating the Team, Site, and Contacts with appliances
- Managing the Sites, Contacts, and Teams
- Searching within System Health Insights
- Actions on the Appliance List search results
- Globally accessible menus
- Activity History
- My Query Dashboard
- Account Dashboard
- Appliance Dashboard
- Appliance Update Management
- Security Insights
- Managing alerts
- Frequently Asked Questions
Triggering Data Collect Logs
You can request a new Data Collect log collection from the DataCollects tab if your user account, appliance, and current session meet the required conditions.
Ensure the following requirements are met:
Your role has permission to create a Data Collect request for the appliance.
The appliance is supported for this workflow. The source identifies supported eligibility checks for appliance family and version.
The appliance connectivity component is active and running version v2.0.0 or later.
A previous trigger request is not currently in a blocking state.
The request is not blocked by the backend rate limit.
To trigger Data Collect logs
- Open the application dashboard.
- Go to Support > DataCollects.
- Review the status information shown on the page, including appliance connectivity and support details.
- Click Trigger Data Collect Logs.
- If prompted, complete OTP verification.
- For clustered appliances, select one or more nodes. Nodes that are not eligible for the request are unavailable for selection.
- Review the available options:
Data Masking is enabled by default.
Include application instance logs is available for Flex appliances.
Include advanced logs is available for supported appliance families.
- Click Submit.
For clustered appliances, Submit is enabled only after at least one node is selected.
Data masking can increase the time required to generate logs and may contribute to timeout conditions.
After a successful submission, the trigger action remains unavailable for the rest of the browser session for the same appliance and selected nodes.
While a request is being submitted, the interface prevents another trigger request from being submitted.