change loglevel

This topic describes the change loglevel command in gfsh, the VMware Tanzu GemFire command-line interface.

Use this command to changes the logging level on specified members. This command takes effect when using the default Tanzu GemFire logging configuration.

When using a custom Log4J configuration, this command takes effect only if the member whose logging level you want to change is started using the --J=-Dgeode.LOG_LEVEL_UPDATE_OCCURS=ALWAYS system property.

The change loglevel command applies only to the members specified, whether they are servers or locators. The change does not apply to unspecified or subsequently-added members.

Availability: Online. You must be connected in gfsh to a JMX Manager member to use this command.

Syntax:

change loglevel --loglevel=value [--members=value(,value)*] [--groups=value(,value)*]

Table 1. Change Loglevel Parameters

Name	Description	Default Value
‑‑members	Name or ID of one or more members whose logging level you want to change.
‑‑groups	One or more group names. The logging level changes for all members of these groups.
‑‑loglevel	Required. Log level to change. Valid options are: ALL, TRACE, DEBUG, INFO, WARN, ERROR, FATAL, OFF.

Table 1. Change Loglevel Parameters

Example Commands:

gfsh>change loglevel --loglevel=DEBUG --members=server1

Sample Output:

gfsh>change loglevel --loglevel=DEBUG --members=server1

Summary

                Member            | Changed loglevel
--------------------------------- | -----------------
192.0.2.0(server1:3060)<v1>:24653 | true