Overview

Oracle WebLogic is a platform for developing, running and deploying enterprise Java applications both on-premises and in the cloud. It centralizes application services that include web server functionality, business components such as messaging, and access to backend enterprise systems such as databases.

Oracle WebLogic monitoring with Datadog enables you to:

• Gain awareness of increasing heap size in your Java Virtual Machine (JVM)
• Track server response time
• Monitor session details of web applications
• Track thread pool and messaging services
• Track database connection pool usage

Setup

Installation

The WebLogic check is included in the Datadog Agent package. No additional installation is needed on your server.

1. This check is JMX-based and collects metrics from the Platform MBean Server exported by the JVM, so your WebLogic servers must have JMX Remote Monitoring enabled. See Remote Monitoring and Management for installation instructions.

2. Set the system property -Djavax.management.builder.initial=weblogic.management.jmx.mbeanserver.WLSMBeanServerBuilder to enable these metrics on the Platform MBean Server. This should be enabled in both the WebLogic Server Administration Console and in the server startup scripts. Note: This can and should be done more than once.

   Enable in the Administration Console

   Domain => Configuration => General => Advanced => Platform MBean Server Enabled
   

   Enable in Server Startup Scripts

   -Djavax.management.builder.initial=weblogic.management.jmx.mbeanserver.WLSMBeanServerBuilder
   

   For more information, see the WebLogic documentation.

3. Verify that the PlatformMBeanServerUsed attribute value is set to true in the WebLogic Server Administration Console. The default value is true in WebLogic Server versions 10.3.3.0 and above. This setting can be found in the WebLogic Server Administration Console or configured using the WebLogic Scripting Tool (WSLT).

   Enable in the Administration Console

   Domain (<WEBLOGIC_SERVER>) => Configuration => General => (Advanced) => Platform MBeanServer Enabled
   

   Enable in WLST

   Start an edit session. Navigate to the JMX directory for the domain and use cmo.setPlatformMBeanServerUsed(true) to enable the attribute if it is set to false.

   For example:

   # > java weblogic.WLST
   (wlst) > connect('weblogic','weblogic')
   (wlst) > edit()
   (wlst) > startEdit()
   (wlst) > cd('JMX/<DOMAIN_NAME>')
   (wlst) > set('EditMBeanServerEnabled','true')
   (wlst) > activate()
   (wlst) > exit()
   

   Activate the changes and restart the WebLogic server.

Configuration

1. Edit the weblogic.d/conf.yaml file, in the conf.d/ folder at the root of your Agent’s configuration directory to start collecting your WebLogic performance data. See the sample weblogic.d/conf.yaml for all available configuration options.

   This check has a limit of 350 metrics per instance. The number of returned metrics is indicated when running the Datadog Agent status command. You can specify the metrics you are interested in by editing the configuration.

   To learn how to customize the metrics to collect, see the JMX Checks documentation for more detailed instructions. If you need to monitor more metrics, contact Datadog support.

2. Restart the Agent

Validation

Run the Agent’s status subcommand and look for weblogic under the Checks section.

Data Collected

Metrics

Log collection

1. WebLogic logging services use an implementation based on the Java Logging APIs by default. Clone and edit the integration pipeline if you have a different format.

2. Collecting logs is disabled by default in the Datadog Agent. Enable it in your datadog.yaml file:

   logs_enabled: true
   

3. Uncomment and edit the logs configuration block in your weblogic.d/conf.yaml file. Change the path and service parameter values based on your environment. See the sample weblogic.d/conf.yaml for all available configuration options.

    - type: file
      path: <DOMAIN_DIR>/servers/<ADMIN_SERVER_NAME>/logs/<ADMIN_SERVER_NAME>.log
      source: weblogic
      service: admin-server
      log_processing_rules:
        - type: multi_line
          name: new_log_start_with_date
          pattern: (\####)?<\w{3} (0?[1-9]|[12][0-9]|3[01]), \d{4}
    - type: file
      path: <DOMAIN_DIR>/servers/<ADMIN_SERVER_NAME>/logs/<DOMAIN_NAME>.log
      source: weblogic
      service: domain
      log_processing_rules:
        - type: multi_line
          name: new_log_start_with_date
          pattern: (\####)?<\w{3} (0?[1-9]|[12][0-9]|3[01]), \d{4}
    - type: file
      path: <DOMAIN_DIR>/servers/<SERVER_NAME>/logs/<SERVER_NAME>.log
      source: weblogic
      service: managed-server
      log_processing_rules:
        - type: multi_line
          name: new_log_start_with_date
          pattern: (\####)?<\w{3} (0?[1-9]|[12][0-9]|3[01]), \d{4}
    - type: file
      path: <DOMAIN_DIR>/servers/*/logs/access.log 
      source: weblogic
      service: http-access
      log_processing_rules:
        - type: multi_line
          name: new_log_start_with_date
          pattern: .*\[\d{2}\/(\w{3}|\w{4})\/\d{4}:\d{2}:\d{2}:\d{2} (\+|-)\d{4}\]
   

4. Restart the Agent

Containerized

For containerized environments, see the Autodiscovery with JMX guide.

Events

The WebLogic integration does not include any events.

Service Checks

weblogic.can_connect
Returns OK if the Agent is able to connect to and collect metrics from the monitored WebLogic instance, WARNING if no metrics are collected, and OK otherwise.
Statuses: ok, critical, warning

Troubleshooting

Need help? Contact Datadog support.