LogicMonitor’s Dell EMC PowerStore monitoring package leverages the PowerStore Management REST API to query the PowerStore cluster for a wide variety of health and performance metrics.

Compatibility

As of January 2022, LogicMonitor’s Dell EMC PowerStore package is known to be compatible with:

• Version 2.0.1.0 – 2.0.1.1

Dell EMC does not guarantee compatibility across minor releases, so later releases might render this suite unusable.

Setup Requirements

• Import the LogicMonitor_Collector_Snippets DataSource to ensure that your collector supports the code in this monitoring suite, or update to EA Collector 32.100 or later.

Add Resources into Monitoring

Add your Dell EMC PowerStore cluster into monitoring. For more information on adding resources into monitoring, see Adding Devices.

Obtain Credentials

LogicMonitor must provide the appropriate credentials in order to successfully access the PowerStore resource’s data. These credentials must belong to a user account that has been assigned the following minimum permissions:

Assign Properties to Resources

The following custom properties must be set on the Dell EMC PowerStore resource within LogicMonitor. For more information on setting properties, see Resource and Instance Properties.

The modules in this suite support HTTP connections using a proxy server. You can configure this in the Collector settings, see Configuring your Collector for use with HTTP Proxies, or with the following device host properties. Device host properties take precedence over Collector settings for proxy configurations.

Import LogicModules

From the LogicMonitor public repository, import all Dell EMC PowerStore 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. Data collection will start automatically once the LogicModules are imported.

Troubleshooting

The modules in this package are designed with a debug mode embedded in the data collection scripts. If issues occur, turn on debug mode by setting the variable debug to “true” to get more information in the output when testing the script in the Collector Debug Facility. For more information on testing scripts in the Collector Debug Facility, see Script Troubleshooting.

LogicModules in Package

LogicMonitor’s package for Dell EMC PowerStore consists of the following LogicModules. For full coverage, make sure that all of these LogicModules are imported into your LogicMonitor platform.

The DataSources in this package do not include predefined datapoint thresholds (that is, no alerts will trigger based on collected data). This is because the technology owner has not provided KPIs that can be reliably extended to the majority of users. If needed, manually create custom thresholds to receive alerts for collected data, as discussed in Tuning Static Thresholds for Datapoints.

LogicMonitor’s Dell PowerVault ME4 monitoring package leverages the Dell EMC REST API to monitor the health and performance metrics of the PowerVault ME4 Storage Area Network. LogicMonitor also alerts on the status and health information gathered from the REST API.

Requirements

Add Resources into Monitoring

Add your Dell PowerVault ME4 hosts into monitoring. For more information on adding resources into monitoring, see Adding Devices.

Obtain Credentials

LogicMonitor must provide the appropriate credentials in order to successfully access the PowerVault ME4 resource’s data. The credentials must have at least a read-only access to the API.

Assign Properties to Resources

The following custom properties must be set on the Dell PowerVault ME4 resource within LogicMonitor. For more information on setting properties, see Resource and Instance Properties.

The modules in this suite support HTTP connections using a proxy server. You can configure this in the Collector settings, see Configuring your Collector for use with HTTP Proxies, or with the following device host properties. Device host properties take precedence over Collector settings for proxy configurations.

Import LogicModules

From the LogicMonitor public repository, import all Dell PowerVault ME4 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. Data collection will automatically start after all the LogicModules are imported.

Troubleshooting

The modules in this package are designed with a debug mode embedded in the data collection scripts. If issues occur, turn on debug mode by setting the variable debug to “true” to get more information in the output when testing the script in the Collector Debug Facility. For more information on testing scripts in the Collector Debug Facility, see Script Troubleshooting.

Migration from Legacy LogicModules

If you are currently monitoring Dell PowerVault ME4 controller ports, updating from version 1.0 to version 1.1 will cause data loss to Compact Flash and Controller Expander instances.

LogicModules in Package

LogicMonitor’s package for Dell PowerVault ME4 consists of the following LogicModules. For full coverage, please ensure that all of these LogicModules are imported into your LogicMonitor platform.

When setting static datapoint thresholds on the various metrics tracked by this package’s DataSources, LogicMonitor follows the technology owner’s best practice KPI recommendations. If necessary, we encourage you to adjust these predefined thresholds to meet the unique needs of your environment. For more information on tuning datapoint thresholds, see Tuning Static Thresholds for Datapoints.

LogicMonitor offers an out-of-the-box monitoring suite for the Rubrik Cloud Data Management (CDM) storage system platform. This suite uses Rubrik’s API to query the Rubrik cluster host for health and performance metrics.

Compatibility

As of September 2024, LogicMonitor’s Rubrik package is known to be compatible with:

• Rubrik CDM 9.1x API

Setup Requirements

The following steps are required to set up Rubrik Monitoring in your LogicMonitor environment.

Add Resources into monitoring

Add your Rubrik cluster hosts into monitoring. For more information on adding resources into monitoring, see Adding Devices.

Assign properties to Resources

The following custom properties must be set on the Rubrik resource within LogicMonitor. For more information on setting properties, see Resource and Instance Properties.

The modules in this suite support HTTP connections using a proxy server. You can configure this in the Collector settings, see Configuring your Collector for use with HTTP Proxies, or with the following device host properties. Device host properties take precedence over Collector settings for proxy configurations.

Import LogicModules

Import all Rubrik LogicModules from the LogicMonitor public repository. See the list of LogicModules in Package. If these LogicModules are already present, make sure you have the most recent versions.

Assuming all previous setup requirements have been met, data collection will automatically start once the LogicModules are imported.​

Troubleshooting

The modules in this package are designed with a debug mode embedded in the active discovery and data collection scripts. If issues occur, turn on debug mode by setting the variable debug to “true” to get more information in the output when testing the script in the Collector Debug Facility. For more information on testing scripts in the Collector Debug Facility, see Script Troubleshooting.

LogicModules in Package

LogicMonitor’s package for Rubrik consists of the following LogicModules. For full coverage, make sure that all of these LogicModules are imported into your LogicMonitor platform.

When setting static datapoint thresholds on the various metrics tracked by the DataSources in this package, LogicMonitor follows the Rubrik’s best practice KPI recommendations. If necessary, we encourage you to adjust these predefined thresholds to meet the unique needs of your environment. For more information on tuning datapoint thresholds, see Tuning Static Thresholds for Datapoints.

Overview

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.

Compatibility

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

Setup Requirements

Enable SNMP

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.

Obtain Credentials

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.

Import LogicModules

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.​

Troubleshooting

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.

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.

Overview

LogicMonitor's Infinidat InfiniBox monitoring package leverages the InfiniBox REST API to monitor a large number of health, usage, and performance metrics for this enterprise storage system.​​ ​

Setup Requirements

Add Resources Into Monitoring

Add your InfiniBox resource into monitoring. For more information on adding resources into monitoring, see Adding Devices.

Obtain Credentials

LogicMonitor must provide the appropriate credentials in order to successfully access the InfiniBox system's data. These credentials should belong to a read-only InfiniBox REST API user account. For more information on creating InfiniBox users, see InfiniBox user management. ​​

Assign Properties to Resources

Several custom properties must be set on the InfiniBox resource within LogicMonitor. For more information on setting properties, see Resource and Instance Properties.

Import LogicModules

From the LogicMonitor public repository, import all Infinidat InfiniBox 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.

Note: Be sure to import the addCategory_InfinidatInfinibox PropertySource. In addition to adding the appropriate identifying category value of "InfinidatInfinibox" to the system.categories property, this LogicModule creates the InfiniBox performance monitoring collectors needed to gather metrics.

Once all LogicModules are imported (assuming all previous setup requirements have been met), data collection will automatically commence.

Special Considerations: Creating Custom Performance DataSources

By default, LogicMonitor's performance metric DataSources (these DataSources have names that end in "Performance") only gather system-wide performance metrics. However, custom DataSources can be created if the monitoring of more specific performance aspects is desired.

To accomplish this, perform the following steps:

1. Open the addCategory_InfinidatInfiniBox PropertySource.
2. Uncomment the template lines in the collector presence map to add a new InfiniBox collector property:

   // Grab what's there
         def collectorPresenceMap = [
           /* Template for adding a check for collectors
           MYCOLLECTOR : hostProps.get("auto.infinidat.MYCOLLECTOR.collector", "notPresent"),
           */
           SAN_FC   : hostProps.get("auto.infinidat.SAN_FC.collector", "notPresent"),
           SAN_iSCSI: hostProps.get("auto.infinidat.SAN_ISCSI.collector", "notPresent"),
           SAN_QOS  : hostProps.get("auto.infinidat.SAN_QOS.collector", "notPresent"),
           NAS      : hostProps.get("auto.infinidat.NAS.collector", "notPresent"),
           RMR      : hostProps.get("auto.infinidat.RMR.collector", "notPresent")
         ]

   Groovy

   Copy
3. Uncomment the code in the service map to add the target metrics to the generateCollectorStrings function:

    def serviceMap = [
           /* Add your metrics below
               "MYCOLLECTOR" : [
                         "metric1",
                         "metric2",
                         ],
           */
               "SAN"    : [
                       "throughput",
                       "operation_size",
                       "average_operation_size",
                       "external_latency",
                       "internal_latency",
                       "external_latency_wout_err",
                       "internal_latency_wout_err",
                       "sections_read",
                       "sections_read_from_cache",
                       "sections_read_from_disk",
                       "ops",
                       "aborted_task",
                       "errors"
               ],
               "SAN_QOS": [
                       "qos_latency",
                       "approved_throughput",
                       "approved_ios"
               ],
               "NAS"    : [
                       "average_operation_size",
                       "throughput",
                       "latency",
                       "sections_read",
                       "sections_read_from_cache",
                       "sections_read_from_ssd",
                       "sections_read_from_disk",
                       "ops"
               ],
               "RMR"    : [
                       "ops",
                       "average_operation_size",
                       "throughput",
                       "latency",
                       "sections_read",
                       "sections_read_from_cache",
                       "sections_read_from_ssd",
                       "sections_read_from_disk"
               ]
   

   Groovy

   Copy
4. Uncomment the below code to build the payload string:

    /* tweak the payload before to fit what you're looking for
           https://support.infinidat.com/hc/en-us/articles/360002184398-InfiniBox-IO-Performance-Monitoring-Using-Live-Counters
           
           else if (service == "MYCOLLECTOR"){
               def payload = "{\"filters\":  {\"protocol_type\": \"${service}\"} ,\"type\": \"COUNTER\", \"collected_fields\": ${counters.collect { '"' + it + '"' }}}"
   
               
               if (collectorPresenceMap.get(service).toLowerCase() == "notpresent") {
                   payloadMap.put(service, payload) // create a collector
               }else{
                   println "infinidat.${service}.collector=${collectorPresenceMap.get(service)}" // output valid collector
               }
           }
           */
   

   Groovy

   Copy
5. To build the corresponding DataSource, clone any of the InfinidatInfiniBox*Performance DataSources and change this line:

   def collectorId = hostProps.get("auto.infinidat.rmr.collector", "notPresent")

   ​to

   def collectorId = hostProps.get("auto.infinidat.MYCOLLECTOR.collector", "notPresent")

6. Your custom DataSource should automatically print out all of the counters available from the InfiniBox collector you created in the PropertySource.

LogicModules in Package

​ LogicMonitor's package for Infinidat InfiniBox consists of the following LogicModules. For full coverage, please ensure that all of these LogicModules are imported into your LogicMonitor platform.

When setting datapoint thresholds on the various metrics tracked by this package's DataSources, LogicMonitor follows the technology owner's best practice KPI recommendations. If necessary, we encourage you to adjust these predefined thresholds to meet the unique needs of your environment. For more information on tuning datapoint thresholds, see Tuning Static Thresholds for Datapoints.

Overview

​ LogicMonitor’s SwiftStack monitoring package leverages the SwiftStack Controller API to monitor a large number of storage utilization, CPU, load, and performance metrics.​ ​

Setup Requirements

Add Resources Into Monitoring

​ Add your SwiftStack resource into monitoring. For more information on adding resources into monitoring, see Adding Devices.

Obtain Credentials

LogicMonitor must provide the appropriate credentials in order to successfully access the SwiftStack resource. These credentials must belong to a SwiftStack user account that has been assigned the following permissions:

Assign Properties to Resources

The following custom properties must be set on the SwiftStack resource within LogicMonitor. For more information on setting properties, see Resource and Instance Properties.

Migration from Legacy LogicModules

In July of 2020, LogicMonitor released several new SwiftStack DataSources. The new DataSources contained optimizations and updates that required significant refactoring, resulting in the deprecation of the following five legacy DataSources.

If you are currently using any of these legacy DataSources, you will not experience data loss upon importing the new DataSources. This is because DataSource 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 DataSources are active. For this reason, we recommend that you disable the above-listed DataSources after importing the new set of DataSources and confirming that they are 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 SwiftStack consists of the following LogicModules. For full coverage, please ensure that all of these LogicModules are imported into your LogicMonitor platform.

​ The DataSources in this package do not include predefined datapoint thresholds (that is, no alerts will trigger based on collected data). This is because the technology owner has not provided KPIs that can be reliably extended to the majority of users. If you’d like to receive alerts for collected data, you’ll need to manually create custom thresholds, as discussed in Tuning Static Thresholds for Datapoints.

Overview

Dell SC is a storage system branded as Dell Storage Center or Dell EMC Storage Center. LogicMonitor offers out-of-the-box monitoring for Dell SC based systems, allowing you to monitor various metrics for the storage devices including fan RPM, fan status, temperature, disk status, health status, global object count statistics, and more.

Compatibility

As of May 2020, LogicMonitor’s package for Dell SC is compatible with the following Dell SC based systems and supports the following models:

• Dell Compellent (SC4020, series 40)
• Dell Storage (SC5020, SC5020F, SC7020, SC7020F, SC8000, SC9000, SCv300, SCv360, SCv2000, SCv2020, SCv2080, SCv3000, SCv3020, SCv3200).

Note: As discussed in the Migration from Dell Compellent to Dell SC LogicModules section of this support article, you must use the Dell SC package (and not our Dell Compellent LogicModules) to monitor any of the above-listed systems. However, you should (continue to) use our Dell Compellent LogicModules to monitor any Compellent systems not listed above.

Setup Requirements

Add Resource Into Monitoring

Add your Dell SC devices into monitoring. The device’s IP or hostname must be entered into the IP Address/DNS name field or monitoring will fail. For more information on adding resources into monitoring, see Adding Devices. ​

Enable SNMP

SNMP must be configured on the Dell SC host in order for the DataSources to successfully collect data. For more information on the SNMP values used, see Dell Storage Center Operating Systems (MIB).​

Enter SNMP Credentials

LogicMonitor must provide the appropriate credentials in order to successfully access the Dell SC system via SNMP. For instructions on how to set the appropriate credentials as properties on the resource within LogicMonitor, see Defining Authentication Credentials. ​​

Import LogicModules

From the LogicMonitor repository, import all Dell SC 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), the suite of Dell SC LogicModules will automatically begin collecting data.

Migration from Dell Compellent to Dell SC LogicModules

The Dell SC monitoring package (all DataSource names in this package are prepended with “Dell_SC”) is intended to replace all Dell Compellent and Dell SC Compellent LogicModules (names are prepended with “Dell_Compellent” and “Dell_SC_Compellent” respectively) for monitoring of any of the above-listed systems.

The Dell SC monitoring package was added because, in recent hardware, it’s been discovered that the discovery and collection of important data such as temperature, fans, fan status, and other data has become unreliable as Dell transitions away from the older 1.3.6.1.4.1.16139 Compellent technologies OID to the newer 1.3.6.1.4.1.674.11000.2000.500.1 Dell Storage Center OID. The Dell SC package uses only the latter OID for discovery and collection.

You may see duplicate alerts if you are monitoring compatible Dell SC devices with both the newer Dell SC DataSources and the older Dell (SC) Compellent DataSources. For this reason, we recommend that you disable any Dell Compellent DataSources after importing the new set of Dell SC DataSources and confirming that they are 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 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.

Note: The new Dell SC package does not work with older Compellent systems (see list of supported models in the Compatibility section of this support article) so if you would like to continue monitoring these older systems, do not disable the associated Compellent DataSources.

LogicModules in Package

​ LogicMonitor’s package for Dell SC consists of the following LogicModules. For full coverage, please ensure that all of these LogicModules are imported into your LogicMonitor platform.

When setting static datapoint thresholds on the various metrics tracked by this package’s DataSources, LogicMonitor follows the technology owner’s best practice KPI recommendations. If necessary, we encourage you to adjust these predefined thresholds to meet the unique needs of your environment. For more information on tuning datapoint thresholds, see Tuning Static Thresholds for Datapoints.

Overview

Apache Hadoop is a collection of software allowing distributed processing of large data sets across clusters of commodity hardware. The LogicMonitor Hadoop package monitors metrics for the following components:

• HDFS NameNode
• HDFS DataNode
• Yarn
• MapReduce

​Compatibility

As of February 2020, we have confirmed that our Hadoop package is compatible with version 3.2.1. It may be possible to monitor older versions of Hadoop, but data will not be returned for all datapoints.

Setup Requirements

Enable JMX on Hadoop Host

LogicMonitor collects Hadoop metrics via the REST API rather than directly via JMX. However, metrics are originally collected and stored using JMX and, therefore, JMX must be enabled on the Hadoop host. For more information on enabling JMX, see the “Enabling JMX” section of the Java Applications (via JMX) Monitoring support article.

Add Hosts Into Monitoring

Add your Hadoop host(s) into monitoring. For more information on adding resources into monitoring, see Adding Devices.

Assign Properties to Hadoop Resources

The following custom properties must be set on the Hadoop resource(s) within LogicMonitor. For more information on setting properties, see Resource and Instance Properties.

Note: These ports must be open to the Collector.

Note: To verify the correct port is being used, you should be able to access http://<HOST>:<HTTP_PORT>/jmx and view metrics for each of the various components.

Import LogicModules

From the LogicMonitor repository, import all Hadoop LogicModules, which are listed in the LogicModules in Package section of this support article. Upon import, these LogicModules will be automatically associated with your Hadoop resources, assuming the properties listed in the previous section are assigned. ​

LogicModules in Package

​ LogicMonitor’s package for Apache Hadoop consists of the following LogicModules. For full coverage, please ensure that all of these LogicModules are imported into your LogicMonitor platform.

Configuring Datapoint Thresholds

The Hadoop package does not include predefined datapoint thresholds (in other words, no alerts will trigger based on collected data). This is because the technology owner has not provided KPIs that can be reliably extended to the majority of users. In order to receive alerts for collected data, you’ll need to manually create custom thresholds, as discussed in Tuning Static Thresholds for Datapoints.

Next are some datapoints for which you may want to consider setting thresholds:

• DataSource: Hadoop HDFS DataNode FS State
  • NumFailedVolumes. Datapoint that reports total number of failed volumes.
  • Remaining. Datapoint that reports remaining capacity on the datanode.
• DataSource: Hadoop HDFS NameNode Info
  • NumberOfMissingBlocksWithReplicationFactorOne. Datapoint that reports the number of blocks with only one copy across the cluster.
  • PercentUsed. Datapoint that reports the percentage of used space across the cluster (DFS and non-DFS).
• DataSource: Hadoop HDFS NameNode Status
  • ServiceRestart. Datapoint that returns a value greater than 0 when the service state changes
  • State. Datapoint that returns a status code indicating the status of the Hadoop namenode service.
• DataSource: Hadoop HDFS NameNode FSNamesystem
  • CorruptBlocks. Datapoint that reports the current number of blocks with corrupt replicas.
  • CorruptReplicatedBlocks. Datapoint that reports the number of corrupt blocks that have been replicated.
  • FSState. Datapoint that returns a status code indicating whether the FS is operational or in safe mode.
  • MissingBlocks. Datapoint that reports the current number of missing blocks.
  • MissingReplicationOneBlocks. Datapoint that reports the number of missing blocks with replication factor of 1.
  • NumDeadDataNodes. Datapoint that reports the number of datanodes currently dead.
  • UnderReplicatedBlocks. Datapoint that reports the current number of blocks under replicated.
  • VolumeFailuresTotal. Datapoint that reports the total number of volume failures across all datanodes.
• DataSource: Hadoop Yarn Queue Metrics
  • AppsFailed. Datapoint that reports the number of applications that failed to complete.
• DataSource: Hadoop Yarn Cluster Status
  • NumLostNMs. Datapoint that reports the current number of lost NodeManagers for not sending heartbeats.

Overview

Cisco HyperFlex is a hyper-converged infrastructure platform. With LogicMonitor’s Cisco HyperFlex package, which leverages the Cisco HyperFlex REST API, you can monitor a large number of HyperFlex operations, as outlined in the LogicModules in Package section of this support article.

Compatibility

LogicMonitor’s Cisco HyperFlex package is compatible with all Cisco HyperFlex products/services that comply with the following prerequisites:

• At minimum, version 2.5 of the HyperFlex Data Platform is required (LogicMonitor has verified compatibility through version 4.0, but it is likely that later versions are also compatible; contact us if you have any questions about a particular version’s coverage)
• Valid credentials for HyperFlex Connect
• HyperFlex Connect or Cluster Management IP address is required

Setup Requirements

Add Devices Into Monitoring

Add your Cisco HyperFlex resources into monitoring if they have not yet been added. For more information on adding resources into monitoring, see Adding Devices.

Assign Properties to Resources

LogicMonitor must be able to provide API credentials in order to successfully access the resource. As such, several custom properties must be set on the Cisco HyperFlex resource within LogicMonitor. For more information on setting properties, see Resource and Instance Properties.

Import LogicModules

From the LogicMonitor repository, import all Cisco HyperFlex 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.

Troubleshooting

DataSources will print error messages to the console when present. These errors can be seen in the output when manually polling data (from the Raw Data tab that displays from the Resources page for each DataSource). DataSources are designed to handle errors gracefully and will attempt to grab any available data even when errors occur.

LogicModules in Package

LogicMonitor’s package for Cisco HyperFlex consists of the following LogicModules. For full coverage, please ensure that all of these LogicModules are imported into your LogicMonitor platform.

When setting static datapoint thresholds on the various metrics tracked by this package, LogicMonitor follows the technology owner’s best practice KPI recommendations. If necessary, we encourage you to adjust these predefined thresholds to meet the unique needs of your environment. For more information on tuning datapoint thresholds, see Tuning Static Thresholds for Datapoints.

VMware vSAN is enterprise-class storage virtualization software that, when combined with vSphere, allows you to manage compute and storage with a single platform. It joins all storage devices across a vSphere cluster into a shared data pool, allowing you to scale up or down as your needs change.

Using LogicMonitor’s VMware vSAN package, you can monitor capacity disk performance; front- and back-end performance for vSan-enabled clusters and hosts; and more.

Compatibility

Some datapoints across the various DataSources in the VMware vSAN package may not be available for vSphere versions prior to 6.5.

Setup Requirements

Import LogicModules

From the LogicMonitor Repository, import all VMware vSAN LogicModules, which are listed in the LogicModules in Package section of this support article.

Duplicate Cluster Naming

vSAN allows multiple clusters to have the same names for similar cluster health tests. However, when multiple clusters are monitored by LogicMonitor, this translates to duplicate instance names, which is not supported (i.e. duplicate names are not discovered).

To ensure unique instance names and for searching the relevant clusters, you can add the custom property of “vsan.instanceformat” to the host and assign it a value of “dedupe” (case insensitive). This property appends the cluster ID to the test name (i.e. <test name> [cluster ID]) to avoid duplicate instance names.

Add Devices Into Monitoring

Add your VMware vSAN devices into monitoring. For more information on adding resources into monitoring, see Adding Devices.

Credentials

LogicMonitor uses the VMware API to provide comprehensive monitoring of many VMware products, including vSAN. For this reason, it must be able to provide the appropriate VMware API user account credentials in order to successfully access the API. If you’ve already established monitoring for VMware vCenter or standalone ESXi hosts, as detailed in ESXi Servers and vCenter/vSphere Monitoring, then a user account has already been established and it can be used for vSAN monitoring as well.

With a user account for the VMware API established, the following properties must be set on the VMware vSAN resource(s) within LogicMonitor. For more information on setting properties, see Resource and Instance Properties.

LogicModule in Package

​LogicMonitor’s package contains the following LogicModules. Please ensure that all of these LogicModules are imported into your LogicMonitor platform.

When setting static datapoint thresholds on the various metrics tracked by this integration package, LogicMonitor follows the technology owner’s best practice KPI recommendations. If necessary, we encourage you to adjust these predefined thresholds to meet the unique needs of your environment. For more information on tuning datapoint thresholds, see Tuning Static Thresholds for Datapoints.