Graph of Oracle monitoring tool ignite

For Oracle, what other monitoring tools besides EM and Gridcontrol are available? Maybe precise is also a good choice. I saw a brother in the Forum a few days ago.

For Oracle, what other monitoring tools besides EM and Gridcontrol are available? Maybe precise is also a good choice. I saw a brother in the Forum a few days ago.

For Oracle, what other monitoring tools besides EM and Gridcontrol are available? Maybe precise is also a good choice. I saw a buddy in the Forum a few days ago who simply replied to ignite, I was also curious. I took the time to look at ignite and some people replied to TOra (). I simply compared these tools.

1) EM may be the most direct tool, and its performance indicators and functions are rich. There is still a big difference between 10g and 11g. At the beginning of 12c, the difference is even more obvious. On the one hand, the increase and refinement of Function Points at 11g are enhanced, on the one hand, many functions are removed in 12c, and only a few monitoring functions are retained. Some management functions are included in gridcontrol (OEM. Therefore, OEM is a good tool without doubt, but there are still some limitations in the case of many database instances to be managed.

2) Of course, GridControl is a complementary and enhanced version of the OEM. It does not provide open features in EM. For example, javasuard has a complete GUI implementation. It is a good choice for managing more instances and monitoring system loads. It is possible that the structure of GridControl is relatively complex and requires a repository library, A set of web containers (httpserver) will be built. An agent needs to be deployed on each client to be monitored. The consumption of the agent in 10 Gb is not small, but it is rarely used in 11 GB, however, this type of problem is not found. Some performance problems may be fixed on the one hand, and some functions are simplified and optimized on the other hand. It may be more important for customers to consider the licence issue.

3) for precise, this tool has been used by the customer. In general, the monitoring granularity is still quite fine. It may be more inclined to monitor functions and have insufficient management permissions ,, no more experience, so no comments. The most important thing is billing.

4) for ignite, because it is still quite a new software for myself, I still experience it with the possibility of freshness. Overall, the support for ignite is still relatively large. It supports Oracle, SQLServer, Sybase, DB2 (it seems that MySQL is missing), and supports a wide range of operating systems, windows, linux. its technical architecture is based on J2EE. It uses tomcat as a web Container and uses a lot of js to interact with the frontend and backend. The web framework is basically used, and spring is widely used.

5) compared with TOra, TOra only supports windows, linux, and max OS, But Oracle is the only supported database. It can be seen from its name. Oracle client is also required for running.

After talking about this, let's give a detailed illustration to let people who have never used ignite experience the functions of ignite. Of course, there are still many details, I also pick a thorn.

Installation

When installing windows, you can easily perform the next operation. There are no technical difficulties.

After the installation is complete, enter the prompt url to view the main interface. At this time, according to ignite requirements, you still need to set a repository. This is exactly the same as EM, OEM, and so on.

When repository is set, the interface implementation is still relatively refined, mainly relying on js to interact with the background.

Click Next. You can see that repository supports oracle and SQL Server, but does not support DB2 and Sybase, but the client monitoring is supported.

We chose oracle, Which is powerful for database instance configuration. Supports direct connection (tns is not configured at this time), tns configuration, or a connection string. You also need to provide a dba account as needed to create users and grant permissions. In this way, a user is created in each client.

The newly created user can specify the corresponding data storage tablespace and temporary space. You can also set the contact information.

The last step is the information overview, and initialization starts. These operations will be switched in the same interface, and the user experience is good.

After a simple wait, the repository configuration will be completed.

Add monitoring Node

After the repository configuration is completed, you need to add monitoring nodes.

The steps for adding a node are similar to those for adding a repository node.

The user to be created in the target node is configured.

After the user information is configured, the following implementation method is not good. You need to use the password of the sysdba account to create an utl_con package. If you have concerns about the password, you can also manually execute the creation script. Scripts are all encrypted star text.

If manual execution is required, the execution is as follows:

Then the information overview is displayed. After confirmation, the configuration starts.

Of course, we also encountered some minor problems, such as the following errors. It can be clearly seen that an error occurred when calling with spring. The reason is unknown, because it is no problem to manually create this synonym.

View monitoring

The process of adding nodes is still smooth, and many related nodes can be configured soon. The effect is as follows.

If you want to view detailed information, charts are indispensable. Of course, they also support a lot of details, similar to EM.

Of course, some features still require additional licence. It seems that you have to pay for all the features you want to use.

For detailed monitoring information, the monitoring targets are still relatively detailed from the perspective of disk, cpu, and memory.