Difference between revisions of "Debug Log"
From AgileApps Support Wiki
imported>Aeric |
imported>Aeric |
||
| Line 11: | Line 11: | ||
Use [[Utility_Calls#debug|Functions.debug]] statements in your classes to add entries to the Debug Log. | Use [[Utility_Calls#debug|Functions.debug]] statements in your classes to add entries to the Debug Log. | ||
That Function adds statements at the ''INFO'' severity level. To see those statements in the Debug Log, make sure that the "recording level is set to that level, or lower. You can also use the | That Function adds statements at the ''INFO'' severity level. To see those statements in the Debug Log, make sure that the "recording level is set to that level, or lower. You can also use the [{{DOCHOST}}/javadocs/com/platform/api/Logger.html Logger] functions to add messages at specified severity levels, and to add an additional "type" parameter you can use to filter the log, later. | ||
''Learn more:'' | ''Learn more:'' | ||
Revision as of 18:56, 4 October 2011
Designer > Global Resources > Debug Log
About the Debug Log
Working with the Debug Log
To work with the debug log, you need either of these permissions:
Adding entries to the Debug Log
Use Functions.debug statements in your classes to add entries to the Debug Log.
That Function adds statements at the INFO severity level. To see those statements in the Debug Log, make sure that the "recording level is set to that level, or lower. You can also use the Logger functions to add messages at specified severity levels, and to add an additional "type" parameter you can use to filter the log, later.
Learn more:
- Change the recording level for messages in Developer Configuration
- debug statement
Controlling Severity-Level Visibility
Debug messages have different severity levels. In the Developer Configuration settings, you can specify which severity levels are recorded in the log.
Viewing the Debug Log
- Visit Designer > Global Resources > Debug Log
- Debug Log entries are displayed in a View.
- Use standard Searching and Filtering operations to determine which records are displayed.
Clearing the Debug Log
- Visit Designer > Global Resources > Debug Log
- Click [Clear Debug Log]