This repository has been archived by the owner on Oct 24, 2020. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 85
Logging
Jose Celano edited this page May 5, 2015
·
2 revisions
Logging allows developers to track activities happening inside the code. You could enable logging for BlockCypher SDK. The instructions to enable logging, or any other configuration is described in Adding Configuration Tutorial
Logging modes will depend on mode
, which represents if the call will be made to sandbox or live. Here are the options:
Please note that logging with DEBUG level prints request, response and headers. Please make sure you use INFO, ERROR or WARN level for live environments, and use DEBUG with extreme caution, in sandbox mode.
-
log.LogEnabled
- Options : true, false
- Enables Logging
-
log.FileName
- When using a relative path, the log file is created relative to the .php file that is the entry point for this request. You can also provide an absolute path here
-
log.LogLevel
- Logging level options are based on mode on which SDK is running. Please refer to Logging Levels section of this page to determine. Logging is most verbose in the
DEBUG
level and decreases as you proceed towardsERROR
.WARN
orERROR
would be a recommended option for live environments.
- Logging level options are based on mode on which SDK is running. Please refer to Logging Levels section of this page to determine. Logging is most verbose in the
- Sandbox Mode
-
DEBUG
,INFO
,WARN
,ERROR
. - Please note that,
DEBUG
is only allowed insandbox
mode. It will throw a warning, and reduce the level toINFO
if set inlive
mode.
-
- Live Mode
-
INFO
,WARN
,ERROR
-
mode is not allowed in live environment. It will throw a warning, and reduce the level toDEBUG
INFO
if set inlive
mode.
-
Getting Started
Using Our SDK
Configurations
Extras
External Links