StreamBase log level output settings
Article ID: KB0075988
Updated On:
| Products | Versions |
|---|---|
| TIBCO Streaming | 7 |
Description
StreamBase log level output settings
Issue/Introduction
StreamBase log level output settings
Resolution
See also article: How to dynamically change the StreamBase log level during runtime
In order to get the logging for both stdout and stderr from the StreamBase server, you need to add the following to your command line:
On Linux use: sbd -f sbd.sbconf myapp.sbapp 2>&1 >sbserver.log
On Windows use: sbd -f sbd.sbconf myapp.sbapp >sbserver.log 2>&1
Where "sbd.sbconf" is your configuration file, "myapp.sbapp" is your application file and "sbserver.log" is the name of the text log file where the output will be captured.
To set the log level, use one of:
STREAMBASE_LOG_LEVEL=0
where the most useful levels are:
0 - normal INFO logging
2 - DEBUG logging
3 - TRACE logging
In a production environment only use INFO logging, as DEBUG and TRACE produce a log of output that can interfere with high-speed processing. You may use DEBUG and TRACE level logging in a testing environment usually at the request of Support. There is very little additional information at DEBUG logging that would be valuable to a customer without Support assistance.
It is often better to set a higher log-level for a specific adapter to investigate a problem than to set a higher log-level for the entire server using the adapter properties editor.
In order to get the logging for both stdout and stderr from the StreamBase server, you need to add the following to your command line:
On Linux use: sbd -f sbd.sbconf myapp.sbapp 2>&1 >sbserver.log
On Windows use: sbd -f sbd.sbconf myapp.sbapp >sbserver.log 2>&1
Where "sbd.sbconf" is your configuration file, "myapp.sbapp" is your application file and "sbserver.log" is the name of the text log file where the output will be captured.
To set the log level, use one of:
STREAMBASE_LOG_LEVEL=0
where the most useful levels are:
0 - normal INFO logging
2 - DEBUG logging
3 - TRACE logging
In a production environment only use INFO logging, as DEBUG and TRACE produce a log of output that can interfere with high-speed processing. You may use DEBUG and TRACE level logging in a testing environment usually at the request of Support. There is very little additional information at DEBUG logging that would be valuable to a customer without Support assistance.
It is often better to set a higher log-level for a specific adapter to investigate a problem than to set a higher log-level for the entire server using the adapter properties editor.
Feedback
Yes
No
Powered by
