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 XVI. System Administration
  4. Working with Log Files
  5. Data collector log file naming conventions

Data collector log file naming conventions

Within the directory structure described in Data Collector log file organization section, log files have the following naming convention:

<vendor.product>/<subsystem>#META_<ID>/Probe.log

For example, an EMC Isilon probe from checkinstall would result in a file name similar to:

/opt/aptare/mbs/logs/validation/emc.isilon
/alphpeifr023#META_EA1BA380E95F73C72A72B3B0792111E5
/IsilonClusterDetailProbe.log

Some collectors may have a period of time when they are not processing a specific subsystem. For those periods, logging will occur in an aggregate log file similar to:

/opt/aptare/mbs/logs/validation/emc.isilon
/#META_EA1BA380E95F73C72A72B3B0792111E5
/IsilonClusterDetailProbe.log

See Data collector log file organization.

Feedback

Was this page helpful?
Previous

Data collector log file organization

Next

Sample Vendor.Product Naming Convention

Feedback

Was this page helpful?