1. RESTful Server Runtime Management Interface for Oracle WebLogic Server
  2. Tasks
  3. WLDF Log Search
  4. WLDF Runtime
  5. WLDF Access Runtime
  6. WLDF Data Access Runtimes
  7. Actions

Search A Diagnostics Log

post

/management/weblogic/{version}/serverRuntime/WLDFRuntime/WLDFAccessRuntime/WLDFDataAccessRuntimes/{name}/search

Search this diagnostics log, returning the results in the same text format as the corresponding server-side log files.

Request

Supported Media Types
Path Parameters
Header Parameters
  • The 'X-Requested-By' header is used to protect against Cross-Site Request Forgery (CSRF) attacks. The value is an arbitrary name such as 'MyClient'.
Body ()

Must contain the following fields:

Root Schema : Search Criteria
Type: object
Title: Search Criteria
Show Source

  • Only return records starting at this record id or later.

    This can be used to continue a search that has more matching results than the specified limit field. The previous response will return a nextRecordId. Set fromId to that value and POST again to continue the search.

    This field is optional.

  • Only return records that have been logged in the last n minutes.

    This field is optional. If specified, the value must be greater than zero.

  • The maximum number of matching records that will be returned.

    If there are more available records, then the response will contain the oldest matching records, as well as a nextRecordId that the client can use to continue the search (by setting fromId to its value).

    This field must be specified. The value must be greater than zero.

  • An optional filter that can be used to restrict which records are returned, for example "SEVERITY = 'Info'". See "WLDF Query Language in Configuring and Using the Diagnostics Framework for Oracle WebLogic Server" for more details.

    This field is optional. If not specified, then no filter is applied to the records.

  • Only return records that were logged at this time or later.

    This field is optional. If specified it must be in one the following formats: "yyyy-MM-dd'T'HH:mm:ss.SSSXXX" (e.g. "2016-05-24T13:44:02.349-04:00"), "yyyy-MM-dd'T'HH:mm:ss.SSSXX" (e.g. "2016-05-24T13:44:02.349-0400") or "yyyy-MM-dd'T'HH:mm:ss.SSSX" (e.g. "2016-05-24T13:44:02.349-04").

  • Only return records that were logged earlier than this time.

    This field is optional. If specified it must be in one the following formats: "yyyy-MM-dd'T'HH:mm:ss.SSSXXX" (e.g. "2016-05-24T13:44:02.349-04:00"), "yyyy-MM-dd'T'HH:mm:ss.SSSXX" (e.g. "2016-05-24T13:44:02.349-0400") or "yyyy-MM-dd'T'HH:mm:ss.SSSX" (e.g. "2016-05-24T13:44:02.349-04").

Security
Back to Top

Response

Supported Media Types

200 Response

Returns the matching records in the same text format as the corresponding server-side log files. The records are in chronological order, oldest record first.

If there are more matching records than limit specified in the request body, then the oldest limit matching records are returned, and an extra line is added to the response in the form nextRecordId=nnn. It contains the record id of the next matching record. The client can continue the search by POSTing the same query to this resource again, setting fromId to the value of nextRecordId, instead of specifying lastMinutes or since

Body ()
Root Schema : Results
Type: string
Title: Results
Back to Top

Examples

Start searching a log.

This example uses the POST method to start searching for records in the server log, returning the results as text.

Example Request
curl -v \
--user admin:admin123 \
-H X-Requested-By:MyClient \
-H Accept:text/plain \
-H Content-Type:application/json \
-d "{
  limit: 2,
  query: 'SEVERITY = \'Info' AND USERID = 'admin'',
  lastMinutes: 60
}" \
-X POST http://localhost:7001/management/weblogic/latest/serverRuntime/WLDFRuntime/WLDFAccessRuntime/WLDFDataAccessRuntimes/ServerLog/search
Example Response
HTTP/1.1 200 OK

Response Body:
####
  
   
    
     
     
       <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> 
      
        <> 
       
         <1549548507973> <[severity-value: 64] [rid: 0] [partition-id: 0] [partition-name: DOMAIN] > 
         
         
           ####
           
            
             
              
              
                <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> 
               
                 <> 
                
                  <1549548508037> <[severity-value: 64] [rid: 0] [partition-id: 0] [partition-name: DOMAIN] > 
                  
                  
                    nextRecordId=457

Continue searching a log.

This example uses the POST method to continue searching for records in the server log, returning the results as text.

Example Request
curl -v \
--user admin:admin123 \
-H X-Requested-By:MyClient \
-H Accept:text/plain \
-H Content-Type:application/json \
-d "{
  limit: 2,
  fromId: 457,
  query: 'SEVERITY = \'Info' AND USERID = 'admin'',
}" \
-X POST http://localhost:7001/management/weblogic/latest/serverRuntime/WLDFRuntime/WLDFAccessRuntime/WLDFDataAccessRuntimes/ServerLog/search
Example Response
HTTP/1.1 200 OK

Response Body:
####
  
   
    
     
     
       <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> 
      
        <> 
       
         <1549548509983> <[severity-value: 64] [rid: 0] [partition-id: 0] [partition-name: DOMAIN] > 
         
         
           ####
           
            
             
              
              
                <[ACTIVE] ExecuteThread: '10' for queue: 'weblogic.kernel.Default (self-tuning)'> 
               
                 <> 
                
                  <1549548633097> <[severity-value: 64] [rid: 0:1] [partition-id: 0] [partition-name: DOMAIN] > 
                  
                  
                    nextRecordId=1432
Back to Top