How to change the log level on a running Streaming 10.x application

How to change the log level on a running Streaming 10.x application

book

Article ID: KB0072523

calendar_today

Updated On:

Products Versions
TIBCO Streaming 10.x

Description

Follow the steps shown below to dynamically change the log level of a running Streaming application. This is generally accomplished using the epadmin logging target.

Resolution

First, determine the Engine Name for the running application. This may be done by following the guidance provided in Knowledge article "How to get JVM details on a running Streaming application"

For example, run..
 
epadmin browse services

..from a StreamBase Command Prompt. The output will include the Engine Name (as highlighted in BOLD text below):
 
Browsed State =  Added
Service Name =  eventflow.default-engine-for-com.example.chirp.deploy_app.cluster_name
Service Type =  eventflow
Network Address =  sb://myhost:24335

Next, you may display all loggers for this Engine:
 
epadmin --servicename=deploy_app.cluster_name display logging --enginename=default-engine-for-com.example.chirp

[deploy_app.cluster_name] Engine Name = default-engine-for-com.example.chirp
[deploy_app.cluster_name] Logger Name = ROOT
[deploy_app.cluster_name] Log Level = INFO

[deploy_app.cluster_name] Engine Name = default-engine-for-com.example.chirp
[deploy_app.cluster_name] Logger Name = com.tibco.ep.dtm.audit
[deploy_app.cluster_name] Log Level = INFO

...

Next, change the log level for one (or more) of these Logger Names:
 
epadmin --servicename=deploy_app.cluster_name set logging --enginename=default-engine-for-com.example.chirp --loggername=ROOT --level=DEBUG

[deploy_app.cluster_name] Engine Name = default-engine-for-com.example.chirp
[deploy_app.cluster_name] Logger Name = ROOT
[deploy_app.cluster_name] Previous Log Level = INFO
[deploy_app.cluster_name] New Log Level = DEBUG

To revert this change, issue the reset logging command:
 
epadmin --servicename=deploy_app.cluster_name reset logging --enginename=default-engine-for-com.example.chirp

For further guidance on customizing your logging configuration, refer to the following related Knowledge articles:

Issue/Introduction

Outlines the steps needed to dynamically change the log level of a running Streaming application, without having to stop and restart the application.

Additional Information

Refer to the Streaming Help for more details:
Home > EP Commands > epadmin and epdev References > epadmin-logging