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

Showing content from https://docs.sentry.io/platforms/python/integrations/logging/ below:

Logging | Sentry for Python

Adds support for Python logging.

Install sentry-sdk from PyPI:

The logging integrations is a default integration so it will be enabled automatically when you initialize the Sentry SDK.

Copied

import sentry_sdk

sentry_sdk.init(
    dsn="https://examplePublicKey@o0.ingest.sentry.io/0",
    
    
    send_default_pii=True,
)

Copied

import logging

def main():
    sentry_sdk.init(...)  

    logging.debug("I am ignored")
    logging.info("I am a breadcrumb")
    logging.error("I am an event", extra=dict(bar=43))
    logging.exception("An exception happened")

main()

• There will be an error event with the message "I am an event".
• "I am a breadcrumb" will be attached as a breadcrumb to that event.
• bar will end up in the event's extra attributes.
• "An exception happened" will send the current exception from sys.exc_info() with the stack trace and everything to the Sentry Python SDK. If there's no exception, the current stack will be attached.
• The debug message "I am ignored" will not surface anywhere. To capture it, you need to lower level to DEBUG (See below).

Log records can additionally also be captured as Sentry logs as long as the enable_logs experimental option is True.

Copied

import logging
import sentry_sdk

sentry_sdk.init(
    
    _experiments={
        "enable_logs": True,
    },
)

logging.info("I will be sent to Sentry logs")

To change the default behavior of the logging integration, instantiate the integration manually and pass it to Sentry's init function:

Copied

import logging
import sentry_sdk
from sentry_sdk.integrations.logging import LoggingIntegration




logging.basicConfig(level=logging.INFO)

sentry_sdk.init(
    
    integrations=[
        LoggingIntegration(
            level=logging.INFO,              
            event_level=logging.ERROR,       
            sentry_logs_level=logging.INFO,  
        ),
    ],
)

You can pass the following keyword arguments to LoggingIntegration():

• level (default INFO): The Sentry Python SDK will record log records with a level higher than or equal to level as breadcrumbs. Inversely, the SDK completely ignores any log record with a level lower than this one. If a value of None occurs, the SDK won't send log records as breadcrumbs.

• event_level (default ERROR): The Sentry Python SDK will report log records with a level higher than or equal to event_level as events as long as the logger itself is set to output records of those log levels (see note below). If a value of None occurs, the SDK won't send log records as events.

• sentry_logs_level (default INFO): The Sentry Python SDK will capture records with a level higher than or equal to sentry_logs_level as Sentry structured logs as long as the enable_logs experimental option is True.

  Copied

  sentry_sdk.init(
      
      _experiments={"enable_logs": True},
  )
  

The Sentry Python SDK will honor the configured level of each logger (set with logger.setLevel(level) or logging.basicConfig(level=level)). That means that you will not see any INFO or DEBUG events from a logger with the level set to WARNING, regardless of how you configure the integration. If not set explicitly, the logging level defaults to WARNING.

Sometimes a logger is extremely noisy and spams you with pointless errors. You can ignore that logger by calling ignore_logger:

Copied

from sentry_sdk.integrations.logging import ignore_logger

ignore_logger("a.spammy.logger")

logger = logging.getLogger("a.spammy.logger")
logger.error("hi")  

You can also use before-send and before-breadcrumb to ignore only certain messages. See Filtering Events for more information.

Instead of using LoggingIntegration, you can use two regular logging logging.Handler subclasses that the integration exports.

Usually, you don't need this. You can use this together with default_integrations=False if you want to opt into what the Sentry Python SDK captures. However, correctly setting up logging is difficult. Also, an opt-in approach to capture data will miss errors you may not think of on your own.

See the API documentation for more information.

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