v2 Contract SDK
  • Orbs Contract SDK
  • Getting Started
    • About smart contracts
    • Becoming a Go developer
    • Installing Gamma - local blockchain
    • Deploying your first contract
    • The Orbs Starter Kit
    • Downloading the Contract SDK
  • Orbs Contracts
    • Smart contracts
    • Layout of a contract file
    • Data types (Exported Functions)
    • State
    • Address
    • Events
    • Error handling
    • Calling other contracts
    • Calling Ethereum contract
    • API Reference
    • Limitations of Orbs Contracts
    • Creating a new contract
  • Gamma in Depth
    • Starting and stopping the server
    • Test keys and accounts
    • Deploying smart contracts
    • Sending transactions and queries
    • Checking sent transaction status
    • Reading Logs from Contracts
    • Working with multiple environments
    • Upgrading to latest versions
    • Gamma server under the hood
    • Deploying Gamma in the Cloud
      • Amazon Web Services
      • Google Cloud Platform
      • Azure
Powered by GitBook
On this page
  1. Gamma in Depth

Reading Logs from Contracts

In multiple cases it is required to log information about the execution of your contracts - these logs are intended for development purposes only and should not be a part of your final contract.

During the development lifecycle, it is possible to use println() function from the standard Go library, this will output the message out to the stderr of the server.

In order to 'listen' to these log messages, Gamma-cli enables you to run

gamma-cli logs

which will run indefinitely and listen to the output pipe from within the docker instance which runs the gamma server.

To stop listening, send a break signal using ctrl+c

PreviousChecking sent transaction statusNextWorking with multiple environments

Last updated 5 years ago