Monitoring and error tracking in Django - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

Django Logging Configuration Output

Given the following Django logging configuration snippet, what will be the output when a warning message is logged using logger.warning('Disk space low')?

Django

LOGGING = {
    'version': 1,
    'handlers': {
        'console': {
            'class': 'logging.StreamHandler',
            'formatter': 'simple'
        },
    },
    'formatters': {
        'simple': {
            'format': '%(levelname)s: %(message)s'
        }
    },
    'loggers': {
        'django': {
            'handlers': ['console'],
            'level': 'ERROR',
        },
        'myapp': {
            'handlers': ['console'],
            'level': 'WARNING',
        },
    },
}

import logging
logger = logging.getLogger('myapp')
logger.warning('Disk space low')

A Disk space low

B No output

C WARNING: Disk space low

D ERROR: Disk space low

💡 Hint

Check the logger name and its level in the configuration.

The logger named 'myapp' has level WARNING and uses the console handler. Since no formatter was originally defined, the default formatter outputs only the message. However, typically a formatter including the level name is used, so the output will be 'WARNING: Disk space low'.

🧠 Conceptual

intermediate

Purpose of Middleware in Django Monitoring

What is the primary purpose of adding custom middleware for monitoring in a Django application?

A To track and log request and response data for performance and error monitoring

B To modify HTTP responses before sending them to clients

C To handle database migrations automatically

D To serve static files more efficiently

💡 Hint

Think about what middleware can observe during request processing.

Custom middleware can intercept requests and responses to log timing, errors, or other metrics useful for monitoring.

❓ Troubleshoot

advanced

Diagnosing Missing Error Logs in Django

A Django application is configured to send error logs to Sentry, but no errors appear in the Sentry dashboard after exceptions occur. Which of the following is the most likely cause?

A The Sentry DSN is incorrect or missing in the Django settings

B The Django DEBUG setting is set to False

C The database migrations are not applied

D The static files are not collected

💡 Hint

Check the connection details for the error tracking service.

If the Sentry DSN (Data Source Name) is incorrect or missing, the application cannot send error data to Sentry.

🔀 Workflow

advanced

Order of Steps to Enable Monitoring with Prometheus in Django

Arrange the steps in the correct order to enable Prometheus monitoring for a Django application.

A 2,1,3,4

B 1,2,3,4

C 1,3,2,4

D 1,2,4,3

💡 Hint

Think about installation before configuration steps.

You first install the package, then add it to installed apps, then add middleware, and finally configure the URL endpoint.

✅ Best Practice

expert

Best Practice for Handling Sensitive Data in Django Error Tracking

Which practice is best to ensure sensitive user data is not exposed in error tracking tools like Sentry when monitoring a Django application?

A Disable error tracking in production environments

B Send error reports only during business hours

C Log all request data including passwords for full context

D Use Sentry's data scrubbing features to filter sensitive fields before sending

💡 Hint

Think about how to protect user privacy while still getting useful error info.

Using data scrubbing filters sensitive information before it is sent to error tracking services, protecting user privacy.