Known Issues

The following are known operational/performance issues.

  • Top Processes page takes 1 minute to load data.

    The first time you access the page, or when you do a browser refresh, it will take approximately one minute to load the most recent data. However, you will not see the issue if you switch from Top CPU to Top Memory (or vice-versa) as data for both categories are loaded upon initial page access or page refresh.

  • You cannot have the same middleware home and server name with different domain homes. If there is more than one instance of Weblogic domain on a single Compute instance with the following configuration, they will not get discovered.
    MiddlewareHome1 / DomainHome1 / ServerName1
    MiddlewareHome1 / DomainHome2 / ServerName1
  • Display of Memory Utilization data for DB Instance resource types is not supported in this release.

    Memory Utilization(%) metric is not supported for Oracle Database Instance. Oracle Database processes have shared memory, and using a non-root user, it is not possible to accurately calculate memory across all processes without overcounting. This will be addressed in future releases with support for full monitoring of the Oracle Database.

  • Oracle Pluggable Databases will not be listed in the Monitored Resources page. They are not supported in this release.
  • On Oracle Linux 8, the OS Management service is not enabled by default.

    This will impact the automatic activation after the required policies have been set up. You will first need to manually enable the OS Management service. Consult the OS Management service documentation for details.

  • Make sure none of your Compute instances belong to more than five dynamic groups.

    A good practice is to combine instances whenever possible rather than creating one or more dynamic groups for each service. See Managing Dynamic Groups for more details about this limitation.

  • MySQL Database monitoring: When running multiple MySQL daemons on a single server, these need to be separated with separate configuration files specified using --defaults-file or --defaults-extra-file. Alternatively, usage of --defaults-group-suffix in the same configuration file is supported.