Monitor

Back Next

Server Log

The Server Log captures events occurring on the server so that you can view and troubleshoot problems. For each event, the log includes the time, problem level, source (initiator), service (event type), engine, and message describing the event. For example, a BPR deployment causes a log event with info level, system source, engine service.

The server log may not update immediately after an event occurs. It is typically updated between 30 and 60 seconds after an event. If you are not seeing what you think should be there, you may just need to update your browser.

The following image shows a sample Server Log:

This topic discusses:

Server Log Information

Deleting the Process Server Log

Server Log Information

One of the following filters was used when generating logging information:

Log Time (Logged after and Logged before)
. By default, the log displays the most recent six hours of events. Refresh the page to view the most recent date and time. You can change the log period by setting the date and time. As a time shortcut, you can select the Now
icon at the end of the time text box.

Level
. One of the following was selected:

Verbose—All levels

Info

Warning

Error

Critical

Source
. The initiator of the event or select All. Sources are:

System—Process Server events such as deployments

Maintenance—Storage and deployment log deletions

User—User-initiated

Service
. The services are:

Alert—Alert service configuration events

Email—Email service configuration events

Engine—Engine events, including deployments, Process Server start/stop, storage events, monitoring alerts

Identity—Identity service (file, LDAP, JDBC) configuration events

Messaging—Messaging service (JMS or other) configuration events

Task.—Client URI update events

Process—Messages added to Process Server Log from a process using the Process Server Log Comment system service

All—All services are shown

Engine Name
. The engine upon which execution occurred.

Message
. Text describing the event.

The console records the User/IP address when a purge or scheduling request occurs. An application server may have its own method. Here, for example, is what might be shown for Tomcat:

https://tomcat.apache.org/tomcat-7.0-doc/api/org/apache/catalina/valves/RemoteIpValve.html

Deleting the Server Log

Use the

Clean Up Storage

on the

Storage

tab of the

Server Configuration

page.

In addition, the interface for clearing the server log is available in Process Developer as a system service so that a developer can create and deploy a process to delete the log programmatically.

Logs

Setting the Process Server Logging Level

Deleting the Process Server Log

Download Guide

Watch

Comments

Cloud Application Integration Homepage