Disadvantages of the WebSphere monitoring software TPV (Tivoli performance Viewer)

Shortcomings of TPV
We all know that.
IBM's WebSphere Application Server (WAS) has its own TPV (Tivoli performance Viewer) after V5
Used to monitor the health of was
Includes resources such as JVM memory usage, database connection pool, Web container thread pool, applications, user sessions, transactions, caches, and more
But the main shortcomings of TPV are:
(1) TPV itself is a graphical tool
If you want to use remote
We can only use extra!. X and other graphics terminal login system
Not as easy as Telnet or web system
(2) There are defects in centralized monitoring
If the WebSphere ND version
Then you can monitor all the base nodes that join the ND Unit (cell) in one TPV
One node is a was server
So let's say I have 10 systems with 40 WebSphere servers.
Can all be added to a nd unit to manage it?
The answer is not to be taken
The main reason is two points:
The first is that the TPV will be very slow to start
CPU usage can be very high
Because we're going to connect 40 machines to the soap|. RMI Port
and to read their monitoring levels.
Practice confirms that in a production environment
Once you have added more than 10 base nodes in ND
TPV CPU usage at startup will exceed 50%
and startup success usually takes a long time (depending on system performance, network speed)
If placed in a production environment
Can seriously affect system operation
Second, it's not easy to manage was.
Think of a nd unit with 40 nodes
belong to 10 systems respectively
It's not logically clear.
The usual practice is that a system corresponds to a nd unit
There may be more than one base node in this unit to share the load
(3) There is a flaw in saving performance data
TPV provides a logging mode
Performance data can be stored in an XML file
But one of these XML files is that we look very laborious
Because its format is IBM-default
is not as neat as the database table, and the size of these XML files is growing rapidly
Normally, it's going to be up to G in 1 hours.
Imagine how much trouble we're looking at.

What if I want to log the monitored performance data to a custom log or database? TPV can't do it.
(4) There is insufficient performance alarm
"Performance Advisor" inside TPV
But the people who used it all know
It doesn't really work.
We often encounter was server stop response (hang), downtime (Crash), Memory Overflow (OutOfMemory), etc.
We want to monitor the performance status of was at any time.
And I don't want to keep the TPV.
Want to notify us promptly when was performance exceeds threshold
Like sending an email.
Or on a centralized monitoring platform with pop-up boxes, red tips and other information
None of these TPV can do it.

(5) No report
If I want to see the performance chart of a was server for an hour, day, week, month, or any specified time range
What to do? There is also a lack of TPV in this area
And IBM seems to have no such good tools.

Disadvantages of the WebSphere monitoring software TPV (Tivoli performance Viewer)