Share:|

If you are using a 10.x version of TrueSight Infrastructure Management and you are seeing poor GUI performance and jserver is consuming high levels of CPU when attempting to navigate

through the GUI, we may have something to help.

 

Slowness can have many causes, so Support will likely ask you for your hardware specifications as well as load on the application, and if there are any other outside factors (patching,other applications on the box, network connectivity issues, etc). The goal is to get an overall view of your environment to help narrow down the focus of the search.

 

While there may be a variety of factors, one way to clear up slowness is to enable lazyloading. This is a property which can be set in order to allow more effective loading of objects in the

console.

 

Certain performance problems can be observed within the navigation tree of the Ops Console. Examples of this could be:

 

  •     Navigation tree does not load at all
  •     Navigation tree only partially loads
  •     Navigation tree takes a long time to load
  •     Operations Console becomes inaccessible and the number of https processes increases

 

Setting the lazy loading parameter to true can help to resolve these problems.

 

The performance problems seen in the navigation tree can be caused by a number of things such as:

 

  •     High number of events
  •     High number of dynamic collectors
  •     High number of CIs in the service model
  •     Depth of service model
  •     Large number of component folders
  •     Large number of event folders

 

The recommendation is for users to uncheck those items in the navigation tree preferences that they are not interested in. For example, if a user is interested in events only, then uncheck

the boxes related to service model and folders.

 

This is because of the way the navigation tree works, in that data is loaded in the order of top to down. So, it will be event collectors first, then groups, then service model CIs, then

component folders, then event folders. All of this can take time as they have to be loaded from various sources such as cell, jserver, backend database, and it can result in a bottleneck.

 

The lazyloading option says to load only the toplevel elements. Then as soon as a user wishes to expand that toplevel it will fetch the data at that point. That is why traversing from

toplevel down can seem slower, but it is greatly reducing the load on the jserver.

 

To turn the lazyloading option on, add the following property to pw/custom/conf/pronet.conf file:

    pronet.navtree.lazyloading=true

Then reload the jserver properties with command:

    pw jproperties reload

Then monitor the performance of the TSIM console.

 

If the performance continues to be an issue, there is another property to set in the 10.x versions which can also help with TSIM slowness, the nearcache property.

 

Please add the following properties to the pw/custom/conf/pronet.conf

pronet.hotrod.client.rate.custom.nearcache.enable=false

pronet.hotrod.client.jserver.custom.nearcache.enable=true

pronet.tsim.console.data.fetch.optimized=false

 

Then restart the TSIM server (pw system start). These properties will help to solve performance issues in the TSIM Operations Console and Administration Console and these properties are set by default in TrueSight 11.3.01

 

If the issue remains after enabling the properties above, collect the pw dump 1 output and send the details to Support for further assistance.

 

 

TSIM Component stuck in the “Initializing” state

 

Another issue we have seen recently with TSPS is the TSIM server component being stuck in the Initializing state for a long period of time. While there may be many factors involved in this

type of situation, it is always best to send the logs to Support to review them for other possible causes of the issue.

 

Due to the elastic search errors below the component was unable to communicate (sync) with TSPS which caused it to fail.

INFO 06/21 09:32:53.393 [EventMsg_28] TsimAudit Failed to insert events to ES

java.util.concurrent.ExecutionException: RemoteTransportException[[ZbkOM4q][127.0.0.1:9300][cluster:admin/ingest/pipeline/put]];

nested: ScriptException[compile error]; nested: IllegalArgumentException[Scripts may be no longer than 16384 characters. The passed in

script is 21057 characters. Consider using a plugin if a script longer than this length is a requirement.];

 

This issue with elastic search is fixed in TrueSight 11.3.01 and is tracked as Defect ID: DRTSO-43721. The recommendation is to upgrade to 11.3.01. A workaround is to delete the elastic

 

search data folder and restart TSPS. The elastic search folder can be found here: <TSPS_HOME>/modules/elasticsearch/

Delete the entire folder as it will be recreated upon restart of the TSPS server

 

If clearing the elastic search folder does not allow the TSIM component to initialize, please gather up the output of the tssh dump export command and send it to Support for further review.

 

These were just a couple of issues which we have seen with TrueSight 10.x so we took the time to fix them in 11.3.01 so you will not have to worry about these issues above.

AMIGO.jpg

 

TrueSight 11.3.01 is here!!!!!…

The BMC Assisted MIGration Offering, or AMIGO, is a program designed to assist our customers in planning and preparing for product upgrades from an older, to a newer supported version.  By engaging with BMC Technical Support Analysts, you will be provided with materials containing guidelines and best practices to aid in compiling your own upgrade plan. An upgrade expert will then review your plan, and offer advice and suggestions to ensure success through proper planning and testing.

The AMIGO program consists of a Starter Phase and a Review Phase.  Each phase is initiated by opening a support case, and ends when the case is closed.

In the Starter Phase, an AMIGO Starter case is opened.  Reference material will be provided and a call with a Technical Support Analyst will take place to discuss the details of your upgrade, and address any questions you may have.  The AMIGO Starter case will be closed, and the next step will be for you to prepare a documented upgrade plan.

In the Review Phase, an AMIGO Review case is opened preferably two weeks prior to a set upgrade date.  A call will be scheduled with an upgrade expert to review your detailed plan, providing feedback and recommendations, along with answers to any outstanding questions.  As needed, a follow up discussion with a Technical Support Analyst may take place for feedback after the upgrade is performed.

The AMIGO program includes:

» A “Question and Answer” session before you upgrade

» A review of your upgrade plan with Customer Support

» An upgrade checklist

» Helpful tips and tricks for upgrade success from previous customer upgrades

» A follow-up session with Customer Support to let them know how it went. This will help BMC to enhance the process.

 

To get started, please review the details here:

https://docs.bmc.com/docs/TSOperations/113/amigo-checklist-for-truesight-operations-management-814553031.html

Then open a BMC Support issue containing your environment information (product, version, OS, etc.) and the planned date of the installation, if known. We will contact you promptly, and work with you to ensure a successful and timely outcome.

 

Computer.png

 

 

New Knowledge Added over the last month:

 

000155850     When the TrueSight Agent deployment status is stuck "in progress" or has failed, what troubleshooting details are needed?

 

000156363     TSIM performance is very slow and jserver is consuming high levels of CPU when attempting to navigate through the GUI

 

000156303     If groups are created in the TSIM Admin Console are they exported to the Report Engine for use in Business Objects?

 

000156107     TSIM upgrade or installation hangs on "Configuring and Populating Database" screen on Linux environments

 

000156040     'tssh componenttype update' does not honor the skipResourceCheck


000156341     Running dataUpgrade.bat gives the error “Data upgrade failed! See the logs at DataUpgradeUtility/logs. Please contact BMC support!“

 

000155953     "Self-Monitoring: Server is disconnected from Operations Management Server on <TSPS host name>" events are seen

 

000155948     How can I configure TSIM's jserver process to use an http proxy, so that I can configure the BSR configuration, when a proxy is required to reach the midtier server?

 

000155433     Unable to remove polling interval when editing an existing policy in TSPS

 

000155643     ALARM class events do not appear in the TSPS events display

 

 

 

Looking for a previous blog posting? Find it here: BMC TrueSight Pulse Blogs