To configure WebLogic Monitoring Exporter to scrape metric data from PDC:

1. Download the latest supported version of WebLogic Monitoring Exporter (getN.N.sh) from https://github.com/oracle/weblogic-monitoring-exporter/releases, where N.N is the version number.

   For the list of supported versions, see "Additional PDC Software Requirements" in BRM Compatibility Matrix.

2. Edit the wls-exporter-config.yaml file to include the PDC metrics that you want scraped. For the list of supported metrics, see "WebLogic-Based Application Metrics".

3. Run the following command:

   bash getN.N.sh wls-exporter-config.yaml

   The wls-exporter.war is downloaded to your current directory.

4. Deploy the wls-exporter.war to the server in which PDC is deployed.

WebLogic Monitoring Exporter is deployed on your servers and begins scraping metric data for PDC.

WebLogic Monitoring Exporter exposes your PDC metrics in Prometheus format to the http://localhost:8080/wls-exporter/metrics endpoint on the WebLogic Server.

metricsNameSnakeCase: true
queries:
- key: name
  keyName: location
  prefix: wls_server_
  applicationRuntimes:
    key: name
    keyName: app
    componentRuntimes:
      prefix: wls_webapp_config_
      type: WebAppComponentRuntime
      key: name
      values: [deploymentState, contextRoot, sourceInfo, sessionsOpenedTotalCount, openSessionsCurrentCount, openSessionsHighCount]
      servlets:
        prefix: wls_servlet_
        key: servletName
- JVMRuntime:
    prefix: wls_jvm_
    key: name
- executeQueueRuntimes:
    prefix: wls_socketmuxer_
    key: name
    values: [pendingRequestCurrentCount]
- workManagerRuntimes:
    prefix: wls_workmanager_
    key: name
    values: [stuckThreadCount, pendingRequests, completedRequests]
- threadPoolRuntime:
    prefix: wls_threadpool_
    key: name
    values: [executeThreadTotalCount, queueLength, stuckThreadCount, hoggingThreadCount]
- JMSRuntime:
    key: name
    keyName: jmsruntime
    prefix: wls_jmsruntime_
    JMSServers:
      prefix: wls_jms_
      key: name
      keyName: jmsserver
      destinations:
        prefix: wls_jms_dest_
        key: name
        keyName: destination
 
- persistentStoreRuntimes:
    prefix: wls_persistentstore_
    key: name
- JDBCServiceRuntime:
    JDBCDataSourceRuntimeMBeans:
      prefix: wls_datasource_
      key: name
- JTARuntime:
    prefix: wls_jta_
    key: name

To configure a standalone version of Prometheus for PDC:

1. Configure Prometheus to scrape the PDC metrics exposed by WebLogic Monitoring Exporter.

   To do so, add a scraping configuration to your prometheus.yaml file that is similar to the one shown below for each managed server and admin server in your cluster.

   The following shows a sample admin server configuration for a PDC application that is deployed in the pdc-domain WebLogic domain:

   scrape_configs:
     - job_name: 'wls-metric-pdc'
       scrape_interval: 1s
       metrics_path: /wls-exporter/metrics
       scheme: http
       static_configs:
       - targets: ['hostname:port] #hostname:port of the server where WebLogic Monitoring Exporter resides
         labels:       
           weblogic_domainName: pdc-domain #domain name
           weblogic_domainUID: pdc-domain  #domain UID
           weblogic_serverName: AdminServer #server name
       basic_auth:
         username: username
         password: password  

   where username and password is your WebLogic Server user name and password.

2. Configure the alert rules in Prometheus.

   To do so, add alert rules to your prometheus-rules.yaml file that are similar to the ones shown below:

   groups:  
     -    
       name: alertmanager.rules    
       rules:     
         - alert: heapFreeSizeWarning       
           annotations:         
             message: WLS heap free size is less than 60%.       
           expr: wls_jvm_heap_free_percent{name="AdminServer"} < 60       
           for: 2m       
           labels:         
             domain_uid: pdc-domain         
             severity: critical         
             wls_domain_namespace: {{namespace}}     
         - alert: dataSourceReconnectWarning       
           annotations:         
             message: WLS PricingDB datasource reconnect failed.       
           expr: wls_datasource_failures_to_reconnect_count{name="PricingDB"} > 0       
           for: 2m       
           labels:         
             domain_uid: pdc-domain         
             severity: critical         
             wls_domain_namespace: {{namespace}}     
         - alert: WLSAdminServerNotRunningWarning       
           annotations:         
             message: WLS AdminServer stopped running.       
           expr: wls_server_state_val{location="AdminServer"} != 2       
           for: 2m       
           labels:         
             domain_uid: pdc-domain         
             severity: critical         
             wls_domain_namespace: {{namespace}}     
         - alert: PDCNotRunningWarning       
           annotations:         
             message: PDC stopped running.       
           expr: wls_webapp_config_deployment_state{location="AdminServer",app="PricingDesignCenter",name="AdminServer_/pdc"} != 2       
           for: 2m       
           labels:         
             domain_uid: pdc-domain         
             severity: critical         
             wls_domain_namespace: {{namespace}}            
         - alert: PricingDBRunningWarning       
           annotations:         
             message: PricingDB stopped running.       
           expr: wls_datasource_deployment_state{name="PricingDB"} != 2       
           for: 2m       
           labels:         
             domain_uid: pdc-domain         
             severity: critical         
             wls_domain_namespace: {{namespace}}

3. Configure Prometheus Alertmanager to raise alerts.

   To do so, add alert configurations that are similar to the ones shown below to your prometheus.yaml file.

   # Alertmanager configuration
   alerting:
     alertmanagers:
     - static_configs:
       - targets:
          - localhost:9093
   # Load rules once and periodically evaluate them according to the global 'evaluation_interval'.
   rule_files:
     - "prometheus-rules.yaml"

4. Stop and restart Prometheus.

You can create a dashboard in Grafana for displaying the metric data for PDC.

Alternatively, you can use the sample dashboards that are included with the PDC package. To use the sample dashboards, import the JSON file from the PDC_home/apps/Samples/monitoring directory into Grafana. For information about importing dashboards into Grafana, see "Export and Import" in the Grafana Dashboards documentation.