10.7 SP1 Configuration Changes & Important Post Install Notes

Document created by Charles_Nack Employee on Jun 12, 2018Last modified by Charles_Nack Employee on Jun 28, 2018
Version 2Show Document
  • View in full screen mode

CONFIGURATION CHANGES:

*********************************************************************************************************

IMPORTANT! After you execute the hotfix script and verify the results, but BEFORE you start Enterprise

Manager, we highly recommended for large deployments to set the default value of

the property introscope.enterprisemanager.alerts.maxPeriods to 2000 or higher.

 

Furthermore, if you already have attribute-based Universes or otherwise do not want Domain Universes to appear,

disable the Domain Universes feature by setting the property introscope.apmserver.domainuniverses.enable to false.

 

 

In <EM_HOME>/config/IntroscopeEnterpriseManager.properties:

- The new property is added: introscope.enterprisemanager.alerts.maxPeriods=20

  The Maximum number of observed periods for alerts. The default value is 20 (which is

  equivalent to 5 minutes).

- The new property is added: introscope.apmserver.domainuniverses.enable=true

  This property configures Domain Universe Synchronization. The default value is true.

  Set the value to false to disable synchronization and delete Domain Universes.

- The new property is added: log4j.additivity.Manager.JavaScriptCalculator=false

  This property fixes duplicate messages for the JavaScriptCalculator logger.

 

The below information does not require additional changes. These are newly added in SP1. 

 

In <EM_HOME>/config/telemetry.json:

- The three new metrics are added to the telemetry.json configuration file: Smartstor Duration,

  GC Duration and Edge Count

 

In <EM_HOME>/config/APMSqlServer.properties

- The new property is added: com.ca.apm.sqlserver.buffer.directory=

  The directory on which APMSQL temporary buffer will be written, if it is empty or

  directory is invalid, it will redirect to the temp directory.

  Eg. Windows : C://APM/buffer/ and Linux : /root/APM/buffer/

 

In <EM_HOME>/config/modules/APMInfrastructureMM.jar

- The Cloudfoundry metric expression for the metric grouping "Agents - MemInUsePercent" is modified to

"Cloudfoundry\|Orgs\|[^|]*\|Spaces\|[^|]*\|Application\|[^|]*\|[^|]*:Memory Usage Percentage".

- The Cloudfoundry metric expression for the metric grouping "Agents - DiskInUsePercent" is modified to

"Cloudfoundry\|Orgs\|[^|]*\|Spaces\|[^|]*\|Application\|[^|]*\|[^|]*:Disk Usage Percentage".

 

In <EM_HOME>/config/modules/DefaultMM.jar

- The AWS metric expression for the metric grouping "CPU Utilization" is modified to

"AWS\\|Region\\|[^|]*\\|EC2_INSTANCES\\|[^|]*:CPUUtilization".

- The Cloudfoundry metric expression for the metric grouping "CPU Utilization" is modified to

"Cloudfoundry\|Orgs\|[^|]*\|Spaces\|[^|]*\|Application\|[^|]*\|[^|]*:CPU Percentage".

- The AWS metric expression for the metric grouping "Docker Status Value" is removed.

- The new Alert "AWS Status Value" is added. This alert is triggered when the AWS instances

  are not in Running state.

4 people found this helpful

Attachments

    Outcomes