Previous Topic: Troubleshooting: A Metric Family is Not Supported

Troubleshooting › Troubleshooting: A Metric Family is Incomplete

Troubleshooting: A Metric Family is Incomplete

Symptom:

I successfully imported a custom metric family, but found a defective metric definition afterwards. For example, the <Name> property has a maximum length of 32 characters. If this limit is exceeded, it can cause synchronization problems.

Solution:

Carefully delete the custom metric family, as follows:

  1. Locate the IMDataAggregator/apache-karaf-2.3.0/deploy directory.
  2. Delete the XML files that were created and deployed for the metric family. They are named as follows:

    If applicable, also delete the file that was created for the vendor certification:

  3. Restart Data Aggregator by running the following command: 
    service dadaemon restart

    After Data Aggregator restarts, verify that the previously imported metric family or vendor certification does not appear in CA Performance Center. Also, all previously discovered components for this custom certification are deleted.

  4. Click Admin, Data Sources in CA Performance Center.
  5. Select Data Aggregator and click the Resync button.

    The components for remaining metric families synchronize between Data Aggregator and CA Performance Center.

  6. Edit and correct your custom metric family XML file.
  7. Import your corrected metric family XML file.

Troubleshooting: A Vendor Certification Expression is Erroneous

Symptom:

The MVEL compiler may not give an evaluation exception (error) for bad expressions. This situation can happen for somesyntax errors, including but not limited to missing or open parentheses, and multiple asterisks.

The incorrect expression is compiled and no error condition is visible until an expression evaluation is performed with the appropriate variables. Database columns that are the target for the intended expression are not populated.

Solution:

Turn on debug logging for the ExpressionEvaluator using the following steps:

  1. Locate the IMDataAggregator/apache-karaf-2.3.0/etc directory.
  2. Open the org.ops4j.pax.logging.cfg file and create the following entry: 
    log4j.logger.com.ca.im.core.expressionevaluator=DEBUG
  3. Restart Data Aggregator by running the following command: 
    service dadaemon restart
  4. Search for evaluation exceptions in the karaf.log file in the IMDataAggregator/apache-karaf-2.3.0/data/log directory.