DX Application Performance Management

When working with the Management Module Editor, it does not respond

When selecting any metric grouping option, Dasboards, they do not respond.

I checked my CPU and it stays between 10% and 20%, the memory stays at 4.52 GB.

The resources of my server are 8 GB of RAM

What could be happening?

The other applications work correctly, the problem is with the Management Module Editor

Hi Emmanuel,

The slow MM Editor performance could be due to a MOM performance problem.

Please post the MOM perflog.txt & IntroscopeEnterpriseManager.properties files to this thread and I will take a quick look.

Thanks

Lynn

Hi Lynn 

I could not attach the MOM file perflog.txt

But these are the first lines of the file

3/30/18 04:26:15 PM CST,6316,989,130,53,0,3930,72,12,108054,757391,93,0,14122,118,3,0,0,0,283,55,495230,0,0,0,0,0,0,
3/30/18 04:26:30 PM CST,Performance.Heuristics.PerstInsertionTime.Per.Interval,Performance.JVM.TotalMemory,Performance.JVM.FreeMemory,Performance.JVM.GCTimePercent,Performance.Workstation.NumberOfWorkstations,Performance.Harvest.HarvestDuration,Performance.Smartstor.Duration,Performance.Agent.ConnectionThrottleCount,Performance.Agent.NumberOfMetrics,Number of Historical Metrics,Performance.Agent.NumberOfAgents,Performance.Agent.MetricDataPending,Performance.Agent.MetricDataRate,Performance.Server.NumberOfMetricGroups,Performance.Transactions.Num.Inserts.Per.Interval,Performance.Transactions.Num.Dropped.Per.Interval,Performance.Transactions.Num.Queries.Per.Interval,Performance.Transactions.Query.Time.Per.Interval,Performance.Transactions.Index.Insertion.Time.Per.Interval,Performance.Transactions.Data.Insertion.Time.Per.Interval,Performance.Transactions.Num.Traces,Performance.Transactions.TT.Queue.Size,Performance.MetricDataManager.QueryRate,Performance.MetricDataManager.QueryMemory,Performance.Server.NumberOfMapEntityMetricGroups,Queries per interval,Queries duration (ms),
3/30/18 04:26:30 PM CST,0,989,137,30,0,109,34,12,107487,757391,94,0,15925,118,1,0,0,0,69,11,495231,0,0,0,0,0,0,
3/30/18 04:26:48 PM CST,0,989,206,51,0,128,38,12,106764,757391,94,0,21504,118,23,0,0,0,283,114,495254,3,0,0,0,0,0,

Hi jemartineza,

Has the Management Module Editor worked fine before? If so, when did the problem started and has there been any change (new custom MM deployment, new metric grouping/calculator created etc) prior to the problem?

Are you seeing any warning/error regarding loading Management Module in the EM log during EM start up?

Can you check how is the memory/heap usage on the EM itself (not the server memory) when Management Module Editor is accessed?

Thanks,

Aryne

Hello Aryne

So far we have only worked with one Board, and some metrics have been modified, filtering information

Previously if it worked correctly. The server and Introscope services had already been restarted.

When I connect to the Introscope workstation, it shows the message "connecting with the company administrator"

sometimes it takes to connect up to 10 min

Hi Emmanuel,

If the workstation login is taking 10 minutes then it seems the slowness symptoms are not specific to the MM editor. 

Looking at your perflog.txt lines the 3rd column Performance.JVM.TotalMemory shows only 989 so it looks like you are just using the default of 1GB (1024M) for the MOM max heap (-Xmx) which is normally far too small for a cluster.

Assuming you are not running EMs as Windows Services what values do you have for -Xmx & -Xms in the MOM & Collector Introscope_Enterprise_Manager.lax files (see "lax.nl.java.option.additional")

Thanks

Lynn

 jemartineza

Agree with Lynn_Williams increase heap size to 4GB. Increase Xms and Xmx value to 4GB.

=-Xms4096m -Xmx4096m restart your MOM and see if you are  still facing the same problem.

Thanks

Hello

In what file is the modification made?

Hi jemartineza,

Looking at the screen shot you provided above, it seems that your Introscope Enterprise Manager is started as a Windows Service. If this is indeed the case, you will need to modify the heap size in the <EM_Home>\bin\EMService.conf instead.

For example:

Change these:

# Initial Java Heap Size (in MB)
wrapper.java.initmemory=1024

# Maximum Java Heap Size (in MB)
wrapper.java.maxmemory=1024

To these:

# Initial Java Heap Size (in MB)
wrapper.java.initmemory=4096

# Maximum Java Heap Size (in MB)
wrapper.java.maxmemory=4096

Then restart the EM service.

Hope that helps

Very good point Aryne!

The Introscope_Enterprise_Manager.lax file is not used when running EM as a Windows service so any changes in there will have no impact and it is the EMService.conf that needs to be changed: EMservice.conf - CA Application Performance Management - 10.5 - CA Technologies Documentation 

Similarly for running WebView as a service the file WVService.conf is used instead of Introscope_WebView.lax.

Set in the Introscope_Enterprise_Manager.lax file that is located in the <EM_Home> directory.

Also see this doc page for more details: 

Enterprise Manager Tuning - CA Application Performance Management - 10.5 - CA Technologies Documentation 

Make the modifications to the filesMake the modifications to the files and still unable to connect

- Introscope_Workstation.lax

- workstation.jsp

Indicates this the perflog.txt file

4/05/18 08:13:30 PM CDT,0,989,251,24,0,107,14,12,93596,831951,98,0,5871,118,2,0,0,0,120,26,563574,0,0,0,0,0,0,4/05/18 08:13:45 PM CDT,Performance.Heuristics.PerstInsertionTime.Per.Interval,Performance.JVM.TotalMemory,Performance.JVM.FreeMemory,Performance.JVM.GCTimePercent,Performance.Workstation.NumberOfWorkstations,Performance.Harvest.HarvestDuration,Performance.Smartstor.Duration,Performance.Agent.ConnectionThrottleCount,Performance.Agent.NumberOfMetrics,Number of Historical Metrics,Performance.Agent.NumberOfAgents,Performance.Agent.MetricDataPending,Performance.Agent.MetricDataRate,Performance.Server.NumberOfMetricGroups,Performance.Transactions.Num.Inserts.Per.Interval,Performance.Transactions.Num.Dropped.Per.Interval,Performance.Transactions.Num.Queries.Per.Interval,Performance.Transactions.Query.Time.Per.Interval,Performance.Transactions.Index.Insertion.Time.Per.Interval,Performance.Transactions.Data.Insertion.Time.Per.Interval,Performance.Transactions.Num.Traces,Performance.Transactions.TT.Queue.Size,Performance.MetricDataManager.QueryRate,Performance.MetricDataManager.QueryMemory,Performance.Server.NumberOfMapEntityMetricGroups,Queries per interval,Queries duration (ms),4/10/18 06:57:00 PM CDT,0,989,450,0,0,94,92,12,59144,867348,113,0,43553,118,8,0,1,13,390,60,491087,0,2,0,0,0,0,4/10/18 06:57:15 PM CDT,0,989,268,0,0,119,117,12,57851,867362,116,0,43071,118,8,0,2,31,376,94,491096,0,4,0,0,0,0,4/10/18 06:57:30 PM CDT,0,989,352,0,0,82,97,12,60598,867362,119,0,51454,118,7,0,5,72,491,72,491103,0,1,0,0,0,0,4/10/18 06:57:45 PM CDT,3215,989,276,0,0,75,149,12,61104,867362,116,0,49560,118,6,0,1,24,376,66,491108,0,2,0,0,0,0,4/10/18 06:58:00 PM CDT,0,989,370,0,0,102,115,12,61488,867362,115,0,54598,118,21,0,1,14,473,97,491129,0,1,0,0,0,0,4/10/18 06:58:15 PM CDT,0,989,210,0,0,93,90,12,61566,867362,117,0,48916,118,9,0,1,13,368,71,491138,1,3,0,0,0,0,4/10/18 06:58:30 PM CDT,0,989,333,0,0,86,113,12,61104,867362,117,0,42882,118,8,0,2,34,434,86,491147,0,1,0,0,0,0,

Hi Emmanual,

It is the Enterprise Manager configuration that needs to be changed (not the Workstation).

Your perflog.txt is still showing Performance.JVM.TotalMemory = 989 MB .

Please see Aryne 's post above about changing the EM heap in the EMService.conf file instead of the Introscope_Enterprise_Manager.lax file because you are running the EM as a Windows Service (sorry I missed that when you first posted your screenshot)

https://communities.ca.com/thread/241795050-problems-with-management-modules-editor-presents-slowness#comment-242056940 

Thanks

Lynn

Hi Lynn

I made the recommended modifications, although sometimes it takes more than 10 minutes to resolve or not to connect.

----------File information perflog.txt ----

4/11/18 01:00:45 PM CDT,Performance.Heuristics.PerstInsertionTime.Per.Interval,Performance.JVM.TotalMemory,Performance.JVM.FreeMemory,Performance.JVM.GCTimePercent,Performance.Workstation.NumberOfWorkstations,Performance.Harvest.HarvestDuration,Performance.Smartstor.Duration,Performance.Agent.ConnectionThrottleCount,Performance.Agent.NumberOfMetrics,Number of Historical Metrics,Performance.Agent.NumberOfAgents,Performance.Agent.MetricDataPending,Performance.Agent.MetricDataRate,Performance.Server.NumberOfMetricGroups,Performance.Transactions.Num.Inserts.Per.Interval,Performance.Transactions.Num.Dropped.Per.Interval,Performance.Transactions.Num.Queries.Per.Interval,Performance.Transactions.Query.Time.Per.Interval,Performance.Transactions.Index.Insertion.Time.Per.Interval,Performance.Transactions.Data.Insertion.Time.Per.Interval,Performance.Transactions.Num.Traces,Performance.Transactions.TT.Queue.Size,Performance.MetricDataManager.QueryRate,Performance.MetricDataManager.QueryMemory,Performance.Server.NumberOfMapEntityMetricGroups,Queries per interval,Queries duration (ms),

4/12/18 11:13:45 AM CDT,0,4012,1387,0,0,131,59,12,89932,886217,143,0,29303,118,15,0,1,14,705,115,447810,0,0,0,0,0,0,
4/12/18 11:14:00 AM CDT,0,4012,1647,0,0,97,67,12,80946,886217,132,0,35231,118,27,0,2,28,645,126,447834,11,0,0,0,0,0,
4/12/18 11:14:15 AM CDT,0,4012,1305,0,0,115,83,12,80945,886259,132,0,29367,118,12,0,2,25,366,87,447846,3,1,0,0,0,0,

Hi Emmanuel,

I can see that Performance.JVM.TotalMemory is now showing 4012 (MB)

Do you think there has there been an improvement in the overall performance and the UI slowness is now more intermittent?

It may be that additional MOM/cluster performance tuning is required. If performance is still a concern I would suggest you create a new Support case and we can then review your setup in more detail.

https://comm.support.ca.com/csupport/CaseManagement/cases/new 

Thanks

Lynn