Ransomware attackers specifically target and attempt to destroy backup systems to increase the probability of payment. Hardening your system is critical. Please ensure you have reviewed your platform security using the Security Hardening Checklist
Cohesity

COHESITY Documentation

Explore our documentation to get started, discover products & new features, access troubleshooting guides, register sources, platforms support.

Products
Data Security Alliance
Visit Cohesity.com
Demos
Support
Blogs
Developers
Partner Portals
Cohesity Community
© 2026 Cohesity, Inc. All Rights Reserved.
Terms of Use|
Privacy Policy|
Legal|
  1. Home
  2. IT Analytics Help
  3. Section IV. End user
  4. Manage and monitor data collection
  5. View data collection status

View data collection status

Collection status, available at the data collector, policy and probe level, provides results for the last time collection was attempted. Collection is schedule-based and can also be run on-demand for certain vendors. When policies are created, a schedule is set, but collection may not enabled. Because the status is relevant to the conditions you are troubleshooting, you can view a status if the schedule is enabled or disabled.

To View Data Collection Status

  1. Navigate to Admin>Data Collection>Collection Status. By default, the grid is organized by Probe Name.
  2. Organize the grid to your preference. You can use Quick Filters to efficiently sort the data with pre-defined options, or use the Advanced Filter to build a more granular query.

    See Organize the collection status view.

  3. Evaluate the collection Status. Click the status icon to display details.
    • Success - Data collection has successfully completed. The last run of each probe in a policy, including an On-Demand run is successful.

    • Warning - Data collection has completed with some errors. The last run of each probe in a policy, including an On-Demand run is complete and any probe is:

      • Successful and there are error messages in the collector log

      • Canceled or skipped. If an On-Demand collection is running, the scheduled run is skipped.

    • Failure - Data collection has failed to complete. The last run of each probe in a policy, including an On-Demand run is complete and any probe is:

      • Interrupted which indicates that collection was running and stopped during the run. For example, when services are stopped or the receiver monitor thread detects that a Collector is not running, any On-Demand Runs or Scheduled collections In Progress are marked as Interrupted. For scheduled runs, restarting the services, marks the previous In Progress collection as Interrupted as well. For On-Demand runs, restarting the services, results in the On-Demand run starting again.

      • Canceled with an error for any probe in the policy (only applicable for On-Demand runs)

      • Canceled with success for any probe in the policy and fatal error messages in the collector log (only applicable for On-Demand runs)

Feedback

Was this page helpful?
Previous

Quick Filters

Next

Troubleshoot data collection status

Feedback

Was this page helpful?