Usage Note 70667: The ability to turn on logging for the Go Layer was added to SAS/ACCESS® Interface to Google BigQuery
The ability to turn on logging for the Go Layer was added to SAS/ACCESS Interface to Google BigQuery. Go Layer logging is usually enabled at only the direction of SAS Technical Support. However, Go Layer logging also allows users to capture and provide additional debugging logs to Google for analysis without the need for special debug modules from SAS.
With these hot fixes, SAS has added options to support logging. The following table describes the options that you can use in the LIBNAME statement:
LIBNAME Option Name |
Values |
Default Value |
Description |
GO_ENABLE_LOGGING |
NO
YES
|
NO |
specifies whether to enable logging in the Go layer |
GO_LOG_FILE |
"path-and-file-name" |
|
specifies the file that contains log information from the Go layer |
GO_LOG_FORMAT |
json
pretty
term
file
plain
message
logfmt
|
json |
specifies the format for trace messages in Go layer logging
JSON - specifies single-line, compact JSON
PRETTY - specifies multi-line, indented JSON
TERM - specifies color terminal output
FILE - specifies *.log file style output
PLAIN - specifies simple level and message format
MESSAGE - specifies message string only
LOGFMT - specifies structured logging of key-value pairs
|
GO_LOG_LEVEL |
ERROR
WARN
INFO
DEBUG
TRACE
|
INFO |
specifies the logging level for Go layer logging
ERROR - indicates that errors have occurred
WARN - provides messages that identify potentially harmful situations
INFO - provides information that highlights the progress of an application
DEBUG - provides detailed information that you can use to debug your application
TRACE - produces the most detailed information about your application
|
Click the Hot Fix tab in this note to access the hot fix for this issue.
Operating System and Release Information
SAS System | SAS/ACCESS Interface to Google BigQuery | Linux for x64 | | |
*
For software releases that are not yet generally available, the Fixed
Release is the software release in which the problem is planned to be
fixed.
Date Modified: | 2024-02-26 12:17:11 |
Date Created: | 2024-02-20 14:11:17 |