Google Cloud Functions
Add the Sentry SDK to your
The GCP integration currently supports only the Python
3.7 runtime environment. If you try to run it with a newer version (such as
3.9), an error message will be displayed (with debug mode on).
You can use the Google Cloud Functions integration for the Python SDK like this:
import sentry_sdk from sentry_sdk.integrations.gcp import GcpIntegration sentry_sdk.init( dsn="https://examplePublicKey@o0.ingest.sentry.io/0", integrations=[ GcpIntegration(), ], # Set traces_sample_rate to 1.0 to capture 100% # of transactions for performance monitoring. # We recommend adjusting this value in production, traces_sample_rate=1.0, ) def http_function_entrypoint(request): # ...
Check out Sentry's GCP sample apps for detailed examples.
The timeout warning reports an issue when the function execution time is near the configured timeout.
To enable the warning, update the SDK initialization to set
sentry_sdk.init( dsn="https://examplePublicKey@o0.ingest.sentry.io/0", integrations=[ GcpIntegration(timeout_warning=True), ], # Set traces_sample_rate to 1.0 to capture 100% # of transactions for performance monitoring. # We recommend adjusting this value in production, traces_sample_rate=1.0, )
The timeout warning is sent only if the timeout in the Cloud Function configuration is set to a value greater than one second.
With the Google Cloud Functions integration enabled, the Python SDK will:
Automatically report all events from your Cloud Functions
You can modify the transaction sample rate using
Issues reports automatically include:
- A link to the stackdriver logs
- Function details
sys.argvfor the function
- Function execution time (in milliseconds)
- Function configured time (in seconds)
- You can add more data as described here
Request data is attached to all events: HTTP method, URL, headers, form data, JSON payloads. Sentry excludes raw bodies and multipart file uploads. Sentry also excludes personally identifiable information (such as user ids, usernames, cookies, authorization headers, IP addresses) unless you set
Each request has a separate scope. Changes to the scope within a view, for example setting a tag, will only apply to events sent as part of the request being handled.
Our documentation is open source and available on GitHub. Your contributions are welcome, whether fixing a typo (drat!) to suggesting an update ("yeah, this would be better").