![]() Valid process names are backgrounder, vizportal, vizqlserver, dataserver (path begins with C:\ProgramData\Tableau\Tableau Server\data\tabsvc\logs\)Ĭhanges TSM logging levels for: clientfileservice, licenseservice, tabadminagent, tabadmincontroller, tabsvcĮxample: \clientfileservice\clientservice_node1-0.logĬhanges TSM logging levels for: control applicationsĮxamples: \clientfileservice\control_clientservice_node1-0.log This table includes both dynamically configurable keys and those that are not dynamically configurable. 2020.4 - adds interactive microservice container ( ) and application server ( ).Ĭonfiguration Keys for Changing Logging Levels.2020.3 - backgrounder ( ), cluster controller ( ), data server ( ), file store ( ), data source properties ( ), and VizQL server ( ).2020.2 - tsm services ( ) and control application services ( ).These logging levels are dynamically configurable, beginning with these versions: If you are only changing logging levels for one or more of these components, and are running the appropriate version of Tableau, you can change the logging levels without restarting Tableau Server. The capability has been expanded in subsequent releases. In version 2020.2 we introduced dynamic configuration. The key you use depends on which component of TSM or Tableau Server you want to change the logging level for. Set logging levels for TSM and Tableau Server processes using tsm configuration set configuration keys. The following logging levels are listed in order of increasing amount of information logged: Logging at the default INFO level only gathers safe environment information. ![]() This means that if you have any sensitive information in an environment variable, it may be included in a log. Note: When logging at the DEBUG level, full environment information is gathered when Tableau starts.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |