Note:

The data post to LAMA from Applicare is not the individual server data. It is the consolidated data of all the servers added in the Application.

The individual server data is available in Applicare console. Applicare calculates the average and post it to LAMA.

The data post will happen only when the controller is running.

Hardware Metrics

1. CPU (%) -  Machine CPU usage. Available in Enterprise -> Summary.

2. Memory (%) - Machine memory usage. Available in Enterprise -> Summary.

3. Disk (%) - Machine disk usage. Available in Server Analyzer -> Disk.

4. Uptime (in minutes) - Availability of the server in the machine. The server uptime is the average per minute. Only if all the servers in the configured Apps are down then the uptime value will be 0. Even if any one of the server is up in the configured Apps then the uptime value will be 1. Available in the Enterprise -> Summary.

Exchange DOC

Application Metrics

1. Request per second - Throughput of the server. Available in Server Analyzer -> App Server.

2. Response Time (microseconds) - Average response time of the server. Available in Server Analyzer -> App Server.

3. Trading Failure API count - Failure count of the trading API's. Available in Key Business Transactions Load Distribution.

4. Client Authentication Failure Auth - Failure count of the client authentication API's. Available in Key Business Transactions Load Distribution.

5. History request per second - Historical throughput of the server. Available in Server Analyzer -> App Server.

6. Historical response Time (microseconds) - Historical average response time of the server. Available in Server Analyzer -> App Server.

7. Log Monitoring - Error logs of the configured Applications. Available in App Analyzer.

Exchange DOC

Network Metrics

1. Bandwidth (%) - It is the average of both the input and output bandwidth utilization of the interface in the router. It is calculated based on the four fields via SNMP.

Input rate in bits / sec - .1.3.6.1.4.1.9.2.2.1.1.6.<InterfaceIndex>
Output rate in bits / sec - .1.3.6.1.4.1.9.2.2.1.1.8.<InterfaceIndex>

Input Utilization:
Input Utilization (%) = ((Input Rates in bits/sec) / (Configured Mbps * 1000000)) * 100;

Output Utilization:
Output Utilization (%) = ((Output Rates in bits/sec) / (Configured Mbps * 1000000)) * 100;

Bandwidth Utilization = (Input Utilization (%) + Output Utilization (%)) / 2;

Example:
Configured Mbps - 300Mbps
Input Utilization (%) = (47575000 / (300 * 1000000)) * 100;
Input Utilization (%) = 15.86

Output Utilization (%) = (157305000 / (300 * 1000000)) * 100;
Output Utilization (%) = 52.44

Bandwidth Utilization = (15.86 + 52.44) / 2
Bandwidth Utilization (%) = 34.15

2. Packet error count - Sum of current Input and output error count of the interface in the router via SNMP. The below OID will give the history value but only current Input and output errors are calculated.

ifinErrors - .1.3.6.1.2.1.2.2.1.14.<interfaceIndex>

ifOutErrors - .1.3.6.1.2.1.2.2.1.20.<interfaceIndex>

currentifinErrors = ifinErrors - PreviousifinErrors
currentifOutErrors = ifOutErrors - PreviousifOutErrors

Packet error count = (currentifinErrors + currentifOutErrors)

Exchange DOC

Note:

The Exchanges have decided to deprecate the below-listed parameters.
Network Latency
DNS Lookup Count

Database Metrics

1. Replication status - It is the availability of the replication. Not the availability of the database.

select process from v$managed_standby where process='<PROCESS_NAME>' fetch first 1 row only

Example:

PROCESS_NAME -  MRP0

Here MRP0 is the process which is doing the replication. If this process is running then the Replication status is Up. Otherwise it will be Down.

2. Replication Queue size - Pending log sync count in the replication.

SELECT MAX(A.SEQUENCE#) FROM V$ARCHIVED_LOG A,v$archive_dest_status b where (a.dest_id='1' or a.applied ='YES') and a.dest_id=b.dest_id group by b.destination,b.ERROR, a.dest_id, thread# order by a.thread#

3. Replication Bandwidth (%) - Bandwidth Utilization of the Database. 

SELECT sum(value) FROM v$sysstat WHERE name IN ('bytes sent via SQL*Net to dblink', 'bytes received via SQL*Net from dblink')

bytes sent via SQL*Net to dblink and bytes received via SQL*Net from dblink will give the history data. 

So the currentbytesSentAndReceived is captured and the bandwidth is calculated using the below formulae.

currentBytesSentAndReceived = bytesSentAndReceived - previousbytesSentAndReceived;
bytesinMbps = currentBytesSentAndReceived * 0.000008
Bandwidth (%) = (bytesinMbps/ Network speed in Mbps) * 100

4. Replication Latency (microseconds) - Time delay occurred on the data transfer.

SELECT VALUE FROM V$DATAGUARD_STATS WHERE UPPER(NAME)='APPLY LAG'

Exchange DOC

LAMA Holiday Configuration

If the Exclude Holidays check box is checked in the Lama configuration then both the data collection and data post will be skipped for LAMA based on the LAMA Holiday Configuration.

LAMA Holidays

Holiday API

The holiday will be checked in two conditions.

1. Holiday API is added in the LAMA Holidays screen

Every day after 12:00 AM the api will be triggered once and check whether that day is holiday or not. If yes then both the data collection and data post will be skipped on that day. Otherwise the data collection and data post will happen on that day.

Note:

It is not mandatory to update the holidays in the LAMA Holidays screen. Because controller will automatically update the holiday details from that API. The holiday details will be updated only for that current day.

2. Holiday API is not added in the LAMA Holidays screen

The holiday condition will be checked fully based on the days configured in the LAMA Holidays screen.

LAMA Logs

By default only error logs and the API check log for LAMA will be printed in the ApplicareAdmin.log file. The log file will be flushed once it reaches 10 MB.

Steps to enable the success log for LAMA.

1. Go to Applicare Advanced Options menu.

2. Add the PostDataToApiJob value in the Enable Custom Logging field.

3. Click the Submit button to save the changes. 

Steps to disable the success log for LAMA.

1. Remove the PostDataToApiJob value in the Enable Custom Logging field.

2. Click the Submit button to save the changes. 

Note:

Controller restart is not required.

LAMA Details 

Red color row - The data post doesn't happen at regular intervals.

Green color row - The data post starts happening at regular intervals.

Error Count Column

1. Red color - If there was any errors posted to LAMA this column will be displayed in red color with the total error count. Click that column to view the error details posted to LAMA.
2. No color with 0 value - No errors are posted to LAMA.
3. No color with NA value - The log metrics configuration is not enabled.