LogicMonitor’s Cohesity monitoring package leverages the alerts from the Cohesity REST API to monitor and alert on the status of Cohesity protection jobs and other processes. LogicMonitor also monitors different metrics of the Cohesity platform like storage capacity and IOPS over time in one platform.
As of October 2020, LogicMonitor’s Cohesity monitoring package is known to be compatible with:
- Version 6.4.1 and above of the Cohesity REST API
- Some LogicModules will work with version 6.3.1 of the API
- LogicModules were not tested with any version less than 6.3.1
A few of the LogicModules in this package only work with Cohesity hardware. SNMP must be configured on the Cohesity server host in order for these LogicModules to successfully collect data. Those LogicModules requiring SNMP access are noted in the LogicModules in Package section of this support article.
Add Resource Into Monitoring
Add the Cohesity platform into monitoring using the full name of the Cohesity system. The IP address of the API endpoint can also work but the DNS name is preferred. For more information on adding resources into monitoring, see Adding Devices.
LogicMonitor must provide the appropriate credentials in order to successfully access the Cohesity REST API. These credentials should belong to a Cohesity API user with read only access. As best practice, do not give the API user more privileges than needed; admin level access is not required. As discussed in the next section, these credentials will be entered as properties on the Cohesity resource.
Assign Properties to Resource
The following custom properties must be set on the Cohesity DataPlatform resource within LogicMonitor. For more information on setting properties, see Resource and Instance Properties.
|cohesity.user||REST API username|
|cohesity.pass||REST API password|
|cohesity.domain||The domain for the cohesity user. The default is ‘local’.|
|Various SNMP credentials|
(the properties required to establish SNMP credentials vary)
|Used only with the hardware LogicModules. The individual properties required to establish SNMP credentials vary depending on the SNMP version being used. See Defining Authentication Credentials for details.|
From the LogicMonitor public repository, import all Cohesity LogicModules, which are listed in the LogicModules in Package section of this support article. If these LogicModules are already present, ensure you have the most recent versions.
Once the LogicModules are imported (assuming all previous setup requirements have been met), data collection will automatically commence.
If an instance of the Cohesity Troubleshooter DataSource displays in the Resources tree, there is most likely a logon failure. Check the values assigned to the cohesity.user, cohesity.password and cohesity.domain properties.
Also ensure the Logicmonitor Collector used by the Cohesity resource has access to the URL for the Cohesity platform. From the Collector, try to access https://hostname/irisservices/api/v1 where hostname is the name of your Cohesity server. You should be prompted for a username and password on this site.
Migration from Legacy LogicModules
In October of 2020, LogicMonitor released its official production package of LogicModules for Cohesity. Some customers may have Cohesity LogicModules that were pre-production.
If you are currently monitoring Cohesity using any of these pre-production LogicModules, you will not experience data loss upon importing the new ones. This is because names have been changed to eliminate module overwriting.
However, you will collect duplicate data and receive duplicate alerts for as long as both sets of LogicModules are active. For this reason, we recommend that you disable the pre-production set after importing the new set and confirming that the new package is working as intended in your environment.
When a DataSource is disabled, it stops querying the host and generating alerts, but maintains all historical data. At some point in time, you may want to delete the legacy DataSources altogether, but consider this move carefully as all historical data will be lost upon deletion. For more information on disabling DataSources, see Disabling Monitoring for a DataSource or Instance.
LogicModules in Package
LogicMonitor’s package for Cohesity monitoring consists of the following LogicModules. For full coverage, please ensure that all of these LogicModules are imported into your LogicMonitor platform.
|addCategory_Cohesity||PropertySource||Identifies if the host is a Cohesity DataProtect or DataPlatform with working API credentials and assigns a value of “cohesity” to the system.categories property.|
|Cohesity_DataPlatform_Alerts||EventSource||Alarm events from the Cohesity API.|
|Cohesity Basic Storage||DataSource||Gathers basic storage information on cluster and alerts when storage usage exceeds 95%. If the API for Cohesity is version 6.3.1 or less, not all fields are populated.|
|Cohesity ClusterStatus||DataSource||The status of the cluster. The cluster uses operations to keep track of the cluster status.|
|Cohesity Consumers Statistics||DataSource||Monitors stats from Cohesity consumers. API version 6.4 or greater.|
|Cohesity Fans||DataSource||Detects fans and polls the speed and state of each fan. Uses SNMP.|
|Cohesity Node Statistics||DataSource||Statistics for a node in a cluster.|
|Cohesity Node Status||DataSource||The current status of a node. API version 6.4.1 and above.|
|Cohesity Node Status V 6.3||DataSource||The current status of a node. API version 6.3.1 and below.|
|Cohesity Power Supplies||DataSource||Detects the power supplies and monitors the state and watts for each power supply. Uses SNMP.|
|Cohesity ProtectedObjects||DataSource||Objects protected and left unprotected by Cohesity.|
|Cohesity Protection Jobs||DataSource||Protection jobs status and information.|
|Cohesity Troubleshooter||DataSource||Checks Cohesity API Credentials.|
|Cohesity Views||DataSource||Monitor View usage on data platforms. Alerts are set in Cohesity.|
Most of the DataSources in this package do not include predefined datapoint thresholds (that is, no alerts will trigger based on collected data). This is because most alerts are provided by Cohesity through their alerting system.
For those LogicModules that do have predefined data thresholds, LogicMonitor followed the technology owner’s best practice KPI recommendations when setting them.
If you’d like to add or adjust datapoint thresholds to meet the unique needs of your environment, see Tuning Static Thresholds for Datapoints.