Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://cloud.google.com/cpp/docs/reference/common/2.33.0/logging below:

C++ Client Libraries | Google Cloud

Stay organized with collections Save and categorize content based on your preferences.

• 2.42.0-rc (latest)
• 2.41.0
• 2.40.0
• 2.39.0
• 2.38.0
• 2.37.0
• 2.36.0
• 2.35.0
• 2.34.0
• 2.33.0
• 2.32.0
• 2.31.0
• 2.30.0
• 2.29.0
• 2.28.0
• 2.27.0
• 2.26.0
• 2.25.1
• 2.24.0
• 2.23.0
• 2.22.1
• 2.21.0
• 2.20.0
• 2.19.0
• 2.18.0
• 2.17.0
• 2.16.0
• 2.15.1
• 2.14.0
• 2.13.0
• 2.12.0
• 2.11.0
• 2.10.1

An overview of logging in the Google Cloud C++ client libraries.

The client libraries never use logging to report errors, but logging can be enabled to help troubleshoot problems when the last error message does not provide a good enough indication of the root cause.

In general, we abide by the following principles:

• Logging should be controlled by the application developer. Unless explicitly instructed, the libraries produce no output to the console, except to emit a message to std::clog immediately before a GCP_LOG(FATAL) terminates the process.
• Logging should have very low cost:
  • It should be possible to disable logs at compile time. They should disappear as-if there were #ifdef/#endif directives around them.
  • A log line at a disabled log level should be about as expensive as an extra if() statement. At the very least it should not incur additional memory allocations or locks.
• It should be easy to log complex objects.
• The logging framework should play well with the C++ iostream classes.
• The application should be able to intercept log records and re-direct them to their own logging framework.

The application needs to do two things to enable logging:

• First, to configure the destination of the logs you must add a backend (see AddBackend) to the default LogSink.
• Second, you must configure what gets logged. Typically, you initialize the *Connection object with a LoggingComponentsOption. Consult the documentation for each *Client class to find what tracing components are available.

At run-time, setting the GOOGLE_CLOUD_CPP_ENABLE_CLOG to a non-empty value configures a LogBackend that uses std::clog. Likewise, setting the GOOGLE_CLOUD_CPP_ENABLE_TRACING=a,b will enable tracing for components a and b across all client objects. The most common components are auth, rpc, and rpc-streams.

Note that while std::clog is buffered, the framework will flush any log message at severity WARNING or higher.

Use the GCP_LOG() macro to log from a Google Cloud Platform C++ library:

void LibraryCode(ComplexThing const& thing) {
  GCP_LOG(INFO) << "I am here";
  if (thing.is_bad()) {
    GCP_LOG(ERROR) << "Poor thing is bad: " << thing;
  }
}

To enable logs to std::clog the application can call:

void AppCode() {
  google::cloud::LogSink::EnableStdClog();
}

As previously noted, this can be switched at run-time using the GOOGLE_CLOUD_CPP_ENABLE_CLOG environment variable.

Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.

Last updated 2025-08-14 UTC.

[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-14 UTC."],[[["This page provides documentation for logging in the Google Cloud C++ client libraries, emphasizing that logging is controlled by the application developer and does not occur by default."],["The libraries offer logging capabilities to help troubleshoot issues beyond what the last error message might indicate, with a focus on minimal performance impact and no extra memory allocations."],["Enabling logs requires configuring a backend for log destinations and setting which components to log, typically done by initializing a `*Connection` object with `LoggingComponentsOption`."],["Logs can be directed to `std::clog` either programmatically via `LogSink::EnableStdClog()` or by setting the `GOOGLE_CLOUD_CPP_ENABLE_CLOG` environment variable at run-time."],["The `GCP_LOG()` macro is used within the libraries to create log entries, and the `GOOGLE_CLOUD_CPP_ENABLE_TRACING` environment variable allows enabling specific components across all client objects."]]],[]]

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4