Logging

The logging commands are accessible from CONFIG mode. Log configuration is not persistent after a reboot.

The logging features available through the CLI are described below:

Table 37.   Logging

Feature	Command
Enable Sentry logging	debug sentry log enable {device | server | both}
Specify filters	debug sentry log filter <tag> {device-id |device-ip | user-id | bundle-id | service-name | config-uuid} <value>
Specify verbosity	debug sentry log verbosity {level_1_lowest|level_2|level_3|level_4_highest}
Disable Sentry logging	no debug sentry log
Delete log filters	no debug sentry log filter <tag>
Disable initialization log messages	no debug sentry init-log
Enable initialization log messages	debug sentry init-log [level_1_lowest|level_2|level_3|level_4_highest]

•To enable Sentry logging, enter config mode and type the following command:

debug sentry log enable {device|server|both}

-

device Optional. Logging is enabled to and from devices.

-

server Optional. Logging is enabled to and from the ActiveSync Server.

-

both Optional. Logging is enabled to and from both devices and the ActiveSync Server. This value is the default if no parameter is specified.

Example of enabling logging to and from devices:

config# debug sentry log enable device Successful

•To create a filter, enter the following command after logging is enabled:

debug sentry log filter <tag> {device-id | device-ip | user-id | bundle-id | service-name | config-uuid} <value>

-

tag The tag name that you are assigning to the filter

-

device-id | device-ip | user-id | bundle-id | service-name | config-uuid The attribute—device id, device ip, or user id—that corresponds to this filter

-

value Specify the value of the attribute

Example of creating a filter for a specific user:

config# debug sentry log filter KensDevice user-id ksmith Successful

You can verify that the filter was created by using the following command, in EXEC mode, to view a list of filters:

config# end #show sentry log filter TAG ENABLED TYPE VALUE KensDevice true user-id ksmith

•To set the log detail level, enter the following command after logging is enabled:

debug sentry log verbosity {level_1_lowest|level_2|level_3|level_4_highest}

-

level_1_lowest Includes HTTP response/request lines and a few supporting operational messages. level_1_lowest is the default setting.

-

level_2 Includes Level 1 content, HTTP headers, and additional operational messages.

-

level_3 Includes Level 1 and Level 2 content and the information associated with the messages.

-

level_4_highest Includes all available log data.

Example of setting the log detail level:

config# debug sentry log verbosity level_1_lowest Successful

•To disable Sentry logging, enter the following command:

no debug sentry log

Example of disabling the Sentry logging:

config# no debug sentry log Successful

•To delete Sentry log filters, enter the following command:

no debug sentry log filter <tag>

-

tag The tag of the filter(s) you want to disable.

If there are multiple filters with the same tag, they will all be deleted.

To delete or disable specific filters, use the web user interface. For information about deleting filters using the web interface, see Deleting filters. For information about disabling filters using the web interface, see Disabling filters.

Example of deleting filters using the CLI:

config# no debug sentry log filter KensPhone Successful

•To disable log messages during Standalone Sentry initialization, enter the following command:

no debug sentry init-log

Example of disabling log messages during Standalone Sentry initialization:

config# no debug sentry init-log Restart tomcat service to take this effective.

•To enable log messages during Standalone Sentry initialization, enter the following command:

debug sentry init-log [level_1_lowest|level_2|level_3|level_4_highest]

To set log verbosity, enter one of the following options:

-

level_1_lowest Includes HTTP response/request lines and a few supporting operational messages.

-

level_2 Includes Level 1 content, HTTP headers, and additional operational messages.

-

level_3 Includes Level 1 and Level 2 content and the information associated with the messages.

-

level_4_highest Includes all available log data. level_4_highest is the default setting.

Example of setting the log detail level:

config# debug sentry init-log level_2 Restart tomcat service to make this effective.