{"id":155,"date":"2021-12-02T00:00:22","date_gmt":"2021-12-02T00:00:22","guid":{"rendered":"https:\/\/zerotobyte.com\/?p=155"},"modified":"2021-12-20T15:05:13","modified_gmt":"2021-12-20T15:05:13","slug":"introduction-to-django-logging-with-best-practices","status":"publish","type":"post","link":"https:\/\/zerotobyte.com\/introduction-to-django-logging-with-best-practices\/","title":{"rendered":"Introduction to Django logging with Best Practices"},"content":{"rendered":"\n<p><strong>Django logging<\/strong> is one of few basic Django concepts that developers usually neglect but is important to master.<\/p>\n\n\n\n<p>So what exactly is logging?<br><strong>Logging in Django is the process of storing certain records in some form of container (file, database, memory,\u2026) which then helps us in certain stages of development.<\/strong><\/p>\n\n\n\n<p>Firstly, we need to understand the concept of logging, its advantages, disadvantages, and why we use it.<\/p>\n\n\n\n<p>A good understanding, writing, and reading of logs can in the future make debugging easier and, among other things, prevent problems that may occur. While it may not seem like it, the key to <strong>creating large stable Django applications lies in logging.<\/strong><\/p>\n\n\n\n<h2 class=\"wp-block-heading\">What is Django logging?<\/h2>\n\n\n\n<p>Django logging module consists of 4 parts:<\/p>\n\n\n\n<ul><li><strong>Loggers<\/strong> (interface to log events from the application)<\/li><li><strong>Handlers<\/strong> (describes logging behavior, such as writing a message to the screen, to a file, or a network socket)<\/li><li><strong>Filters<\/strong> (providing additional control over recording logs)<\/li><li><strong>Formatters <\/strong>(provides control over rendered text &#8211; custom formats, etc.)<\/li><\/ul>\n\n\n\n<p>The simplest example of using a logging module is shown in the following example:<\/p>\n\n\n\n<p><strong>Example 1.<\/strong><\/p>\n\n\n\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"python\" data-enlighter-theme=\"\" data-enlighter-highlight=\"\" data-enlighter-linenumbers=\"\" data-enlighter-lineoffset=\"\" data-enlighter-title=\"\" data-enlighter-group=\"\">import logging\n\n# logger instance with name of module where it\u2019s used (good practice)\nlogger = logging.getLogger(__name__)\n\nlogger.error(\u201cDummy text\u201d)\n<\/pre>\n\n\n\n<p>And that&#8217;s it, the logger instance is defined and ready to use! <strong>No need to install additional libraries or modules.<\/strong> Plug and play!<\/p>\n\n\n\n<p>Official Django documentation on <a href=\"https:\/\/docs.djangoproject.com\/en\/3.2\/topics\/logging\/\" target=\"_blank\" rel=\"noreferrer noopener\">logging<\/a>.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Loggers, Log levels, and when to use one?<\/h2>\n\n\n\n<p><strong>Loggers have certain log levels<\/strong> that describe events on our backend, let\u2019s dive into it!<\/p>\n\n\n\n<ul><li><strong>DEBUG<\/strong><ul><li>It would be a good practice to use debug method instead of print (read Logging vs printing section)<\/li><\/ul><\/li><li><strong>INFO<\/strong><ul><li>Used to log some general information as well as capture bottlenecks<\/li><\/ul><\/li><li><strong>WARNING<\/strong><ul><li>Describes problems that are small and potentially dangerous, such as missing CSRF_COOKIE<\/li><\/ul><\/li><li><strong>ERROR<\/strong><ul><li>Used when some exception is raised but not caught<\/li><\/ul><\/li><li><strong>CRITICAL<\/strong><ul><li>Never practically used in Django projects<\/li><\/ul><\/li><\/ul>\n\n\n\n<figure class=\"wp-block-table\"><table><tbody><tr><td><strong>Level<\/strong><\/td><td><strong>Numeric value<\/strong><\/td><\/tr><tr><td>CRITICAL<\/td><td>50<\/td><\/tr><tr><td>ERROR<\/td><td>40<\/td><\/tr><tr><td>WARNING<\/td><td>30<\/td><\/tr><tr><td>INFO<\/td><td>20<\/td><\/tr><tr><td>DEBUG<\/td><td>10<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p><strong>All Django logging log levels in the implementation receive the same arguments<\/strong>, ie the structure of arguments (args) and keyword arguments (kwargs) is the same for all -&gt; (msg, * args, ** kwargs).<\/p>\n\n\n\n<p><strong>Kwargs can receive 4 arguments:<\/strong><\/p>\n\n\n\n<ul><li><code class=\"inline-code-style\">exc_info<\/code> <strong>defaults False<\/strong>, if True it causes exception information to be added to logging message<\/li><li><code class=\"inline-code-style\">stack_info<\/code> <strong>defaults False<\/strong>, if True logging message contains stack information till logger is called<\/li><li><code class=\"inline-code-style\">stacklevel<\/code> <strong>defaults 1<\/strong>, if not 1, the exact number of stack frames are skipped when computing the line number and function name<\/li><li><code class=\"inline-code-style\">extra<\/code> dictionary in which we can put whatever information we find useful \ud83d\ude42<\/li><\/ul>\n\n\n\n<p>Let\u2019s see some basic logging examples:<\/p>\n\n\n\n<p><strong>Example 1.<\/strong><\/p>\n\n\n\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"python\" data-enlighter-theme=\"\" data-enlighter-highlight=\"\" data-enlighter-linenumbers=\"\" data-enlighter-lineoffset=\"\" data-enlighter-title=\"\" data-enlighter-group=\"\">from django.http import HttpResponse\nimport logging\n\nlogger = logging.getLogger(__name__)\n\n\ndef my_view(request):\n\n    logging.debug(\"DEBUG\")\n    logging.info(\"INFO\")\n    logging.warning(\"WARNING\")\n    logging.error(\"ERROR\")\n    logging.critical(\"CRITICAL\")\n\n    return HttpResponse(\"Django logging example\")\n<\/pre>\n\n\n\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"raw\" data-enlighter-theme=\"\" data-enlighter-highlight=\"\" data-enlighter-linenumbers=\"\" data-enlighter-lineoffset=\"\" data-enlighter-title=\"\" data-enlighter-group=\"\"><\/pre>\n\n\n\n<p>We come to an interesting output. WARNING, ERROR, and CRITICAL log levels are recorded but we don\u2019t have DEBUG and INFO in the record.<br>This happens because the default level logging is WARNING and all &#8220;less critical&#8221; levels will not be recorded.<\/p>\n\n\n\n<p>We can change this with a simple configuration.<\/p>\n\n\n\n<p><strong>Example 2.<\/strong><\/p>\n\n\n\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"python\" data-enlighter-theme=\"\" data-enlighter-highlight=\"\" data-enlighter-linenumbers=\"\" data-enlighter-lineoffset=\"\" data-enlighter-title=\"\" data-enlighter-group=\"\">from django.http import HttpResponse\nimport logging\n\nlogging.basicConfig(level=logging.DEBUG)\nlogger = logging.getLogger(__name__)\n\n\ndef my_view(request):\n    logging.debug(\"DEBUG\")\n    logging.info(\"INFO\")\n    logging.warning(\"WARNING\")\n    logging.error(\"ERROR\")\n    logging.critical(\"CRITICAL\")\n    return HttpResponse(\"Django logging example\")\n<\/pre>\n\n\n\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"raw\" data-enlighter-theme=\"\" data-enlighter-highlight=\"\" data-enlighter-linenumbers=\"\" data-enlighter-lineoffset=\"\" data-enlighter-title=\"\" data-enlighter-group=\"\">Output:\n\nStarting development server at http:\/\/127.0.0.1:8000\/\nQuit the server with CONTROL-C.\n\nDEBUG:root:DEBUG\nINFO:root:INFO\nWARNING:root:WARNING\nERROR:root:ERROR\nCRITICAL:root:CRITICAL\n\n[26\/Nov\/2021 15:35:59] \"GET \/example\/logging\/ HTTP\/1.1\" 200 22<\/pre>\n\n\n\n<p>Next example shows arguments and keyword arguments usage:<\/p>\n\n\n\n<p><strong>Example 3.<\/strong><\/p>\n\n\n\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"python\" data-enlighter-theme=\"\" data-enlighter-highlight=\"\" data-enlighter-linenumbers=\"\" data-enlighter-lineoffset=\"\" data-enlighter-title=\"\" data-enlighter-group=\"\">from django.http import HttpResponse\nimport logging\n\nlogger = logging.getLogger(__name__)\n\ndef my_view(request):\n    logging.error('Internal server error: %s', request.path,\n                  exc_info=True, #default False\n                  stack_info=True, #default True\n                  stacklevel=1, #default 1\n                  extra={\n                      \"status_code\": 500,\n                      \"request\": request\n                  }\n     )\n\n    return HttpResponse(\"Django logging example\")\n<\/pre>\n\n\n\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"raw\" data-enlighter-theme=\"\" data-enlighter-highlight=\"4,5-10\" data-enlighter-linenumbers=\"\" data-enlighter-lineoffset=\"\" data-enlighter-title=\"\" data-enlighter-group=\"\">Output:\n\nERROR:root:Internal server error: \/example\/logging\/\nNoneType: None\nStack (most recent call last):\n\t. . .\n          File \"...\/django_logging\/venv\/lib\/python3.8\/site-packages\/django\/core\/handlers\/base.py\", line 181, in _get_response\n    response = wrapped_callback(request, *callback_args, **callback_kwargs)\n  File \"...\/django_logging\/example\/views.py\", line 8, in my_view\n    logging.error('Internal server error: %s', request.path,\n\n[26\/Nov\/2021 16:08:15] \"GET \/example\/logging\/ HTTP\/1.1\" 200 22<\/pre>\n\n\n\n<p><code class=\"inline-code-style\">exc_info=True<\/code> outputs NoneType:None because no exception is caught.<\/p>\n\n\n\n<p><code class=\"inline-code-style\">stack_info=True<\/code> produces Stack output (most recent call last)<br><\/p>\n\n\n\n<p>Documentation on <a href=\"https:\/\/docs.python.org\/3\/library\/logging.html#logging.debug\" target=\"_blank\" rel=\"noreferrer noopener\">Module-level functions<\/a>. <\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Handlers and handler classes<\/h2>\n\n\n\n<p><strong>Handlers determine what happens to messages<\/strong>, whether we print them to standard output, to a file, or something else.<\/p>\n\n\n\n<p>Several handler classes are set by default within the logging module, each of which I will briefly describe, and the choice depends on the use case.<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table><tbody><tr><td><strong>Handler<\/strong><\/td><td><strong>Outputs<\/strong><\/td><\/tr><tr><td>StreamHandler<\/td><td>Streams, any object that supports write() and flush()<\/td><\/tr><tr><td>FileHandler<\/td><td>File<\/td><\/tr><tr><td>NullHandler<\/td><td>None<br>usage explained: If you don\u2019t want to produce any logs, it\u2019s easier to change handler to NullHandler instead of removing logs<\/td><\/tr><tr><td>WatchedFileHandler<\/td><td>File<\/td><\/tr><tr><td>BaseRotatingHandler<\/td><td>None<br>Used only for extending (to override methods)<\/td><\/tr><tr><td>RotatingFileHandler<\/td><td>File<br>When the given size is about to be exceeded, a new file is opened<\/td><\/tr><tr><td>TimedRotatingFileHandler<\/td><td>File<br>The new file is opened based on interval or when<\/td><\/tr><tr><td>SockerHandler<\/td><td>Network socket<\/td><\/tr><tr><td>DatagramHandler<\/td><td>Logging messages over UDP sockets<\/td><\/tr><tr><td>SysLogHandler<\/td><td>Logging messages to a remote or local Unix Syslog.<\/td><\/tr><tr><td>NTEventLogHandler<\/td><td>Logging messages to a local Windows NT, Windows 2000, or Windows XP event log.<\/td><\/tr><tr><td>SMTPHandler<\/td><td>Logging messages to an email address<\/td><\/tr><tr><td>MemoryHandler<\/td><td>Logging records in memory<\/td><\/tr><tr><td>HTTPHandler<\/td><td>Logging messages to a web server<\/td><\/tr><tr><td>QueueHandler<\/td><td>Logging messages to a queue<\/td><\/tr><tr><td>QueueListener<\/td><td>Not itself a handler, it is documented here because it works hand-in-hand with QueueHandler<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<pre class=\"wp-block-verse\"><strong>TIP<\/strong> - If unsure use RotatingFileHandler class.<\/pre>\n\n\n\n<pre class=\"wp-block-verse\"><strong>WARNING<\/strong> - WatchedFileHandler should not be used on Windows.<\/pre>\n\n\n\n<h2 class=\"wp-block-heading\">Filter overview<\/h2>\n\n\n\n<p><strong>Filters exist to give us extra control over handlers and loggers.<\/strong><\/p>\n\n\n\n<p>To create your filter inherit the Filter class.<\/p>\n\n\n\n<p>Filter class has a filter method that receives a record in arguments. Also, the Filter class must return True if we want it to enter the logs, otherwise, the log is ignored.<\/p>\n\n\n\n<p>Enough theory, let&#8217;s show what it looks like in practice!<\/p>\n\n\n\n<p><strong>Example 1.<\/strong><\/p>\n\n\n\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"python\" data-enlighter-theme=\"\" data-enlighter-highlight=\"\" data-enlighter-linenumbers=\"\" data-enlighter-lineoffset=\"\" data-enlighter-title=\"\" data-enlighter-group=\"\">import logging\nfrom logging import Filter\n\n\nclass CustomFilter(Filter):\n    MODULE = ['example.views']\n\n    def filter(self, record: logging.LogRecord) -> bool:\n        if record.name in self.MODULE:\n            return False\n        return True\n<\/pre>\n\n\n\n<p>We defined CustomFilter class in which we inherited Filter, in the CustomFilter class we defined the module from which we do not want to receive logs.<\/p>\n\n\n\n<p>In the filter method, we checked whether record.name (name of the module) is in the defined MODULE list, if located we do not record that log.<\/p>\n\n\n\n<p>Let&#8217;s see how we added this filter to the logger instance.<\/p>\n\n\n\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"python\" data-enlighter-theme=\"\" data-enlighter-highlight=\"\" data-enlighter-linenumbers=\"\" data-enlighter-lineoffset=\"\" data-enlighter-title=\"\" data-enlighter-group=\"\">from django.http import HttpResponse\nimport logging\n\nfrom core.logging_filters import CustomFilter\n\nlogger = logging.getLogger(__name__)\ncustom_filter = CustomFilter()\nlogger.addFilter(custom_filter)\n\n\ndef my_view(request):\n    logger.error(\"ERROR\")\n    return HttpResponse(\"Django logging example\")<\/pre>\n\n\n\n<p>Documentation on <a href=\"https:\/\/docs.python.org\/3\/library\/logging.html#filter-objects\" target=\"_blank\" rel=\"noreferrer noopener\">filters<\/a>.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Formatter overview<\/h2>\n\n\n\n<p><strong>Formatter works similarly to the filter<\/strong>, we initialize our Custom class in which we inherit the Formatter class, we have more methods in it that we can override, I will focus on the most used format method.<\/p>\n\n\n\n<p>Let&#8217;s look at the implementation!<\/p>\n\n\n\n<p><strong>Example 1.<\/strong><\/p>\n\n\n\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"python\" data-enlighter-theme=\"\" data-enlighter-highlight=\"\" data-enlighter-linenumbers=\"\" data-enlighter-lineoffset=\"\" data-enlighter-title=\"\" data-enlighter-group=\"\">from logging import Formatter, LogRecord\n\n\nclass CustomFormatter(Formatter):\n\n    def format(self, record: LogRecord) -> str:\n        return \"Any type of information you want in your logs\"\n<\/pre>\n\n\n\n<p><code class=\"inline-code-style\">format<\/code><strong> method returns a string<\/strong> (what will be written in the log file).<\/p>\n\n\n\n<p>The formatter is not added directly to the logger but the handler, as shown in the example:<\/p>\n\n\n\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"python\" data-enlighter-theme=\"\" data-enlighter-highlight=\"\" data-enlighter-linenumbers=\"\" data-enlighter-lineoffset=\"\" data-enlighter-title=\"\" data-enlighter-group=\"\">from logging.handlers import RotatingFileHandler\n\nfrom django.http import HttpResponse\nimport logging\n\nfrom core.logging_formatters import CustomFormatter\n\nlogger = logging.getLogger(__name__)\n\nhandler = RotatingFileHandler('example.log', maxBytes=1000, backupCount=2)\ncustom_formatter = CustomFormatter()\nhandler.setFormatter(custom_formatter)\nlogger.addHandler(handler)\n\n\ndef my_view(request):\n    logger.error(\"ERROR\")\n    return HttpResponse(\"Django logging example\")\n<\/pre>\n\n\n\n<p>Documentation on <a href=\"https:\/\/docs.python.org\/3\/library\/logging.html#formatter-objects\" target=\"_blank\" rel=\"noreferrer noopener\">formatters<\/a>.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Logging vs printing<\/h2>\n\n\n\n<p>Why is it recommended to use a logging library instead of a print?<br><strong>The goal is to have the most detailed view of what we want to show through the application.<\/strong><br>Logging solves it through the log level, in each stage of the code, we can know whether we want to display error, warning, debug, or info.<\/p>\n\n\n\n<p>Additionally, logging can be set to display eg timestamps and other application contexts with a fairly simple configuration. We have more control over the logger, which is always a better thing for a developer.<\/p>\n\n\n\n<p><strong>Print statements are not recorded, unlike logs.<\/strong><\/p>\n\n\n\n<p>Finally, depending on the webserver, a forgotten print statement may crash your entire server.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Django logging tips and best practices<\/h2>\n\n\n\n<ul><li>f-strings don\u2019t work with loggers<\/li><li>use ISO-8601 Format for Timestamps<\/li><\/ul>\n\n\n\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"python\" data-enlighter-theme=\"\" data-enlighter-highlight=\"\" data-enlighter-linenumbers=\"\" data-enlighter-lineoffset=\"\" data-enlighter-title=\"\" data-enlighter-group=\"\">import logging\nlogging.basicConfig(format='%(asctime)s %(message)s') #could be added as formatter\n<\/pre>\n\n\n\n<ul><li>Add logging before the app grows too much \ud83d\ude42<\/li><li>When <code class=\"inline-code-style\">DEBUG=False<\/code> and ERROR log level is triggered, email is sent to every email listed ADMINS<\/li><li>Don\u2019t import and reuse logger from other modules, define a new logger<ul><li>gives you the ability to turn off and on certain loggers<\/li><\/ul><\/li><li>Use log rotation (RotatingFileHandler class) to prevent logs to grow too much<ul><li>the mechanism that is used to prevent full disks<\/li><li>works by compressing and deleting old log files<\/li><\/ul><\/li><\/ul>\n\n\n\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"python\" data-enlighter-theme=\"\" data-enlighter-highlight=\"\" data-enlighter-linenumbers=\"\" data-enlighter-lineoffset=\"\" data-enlighter-title=\"\" data-enlighter-group=\"\">import logging\nfrom logging.handlers import RotatingFileHandler\n\nlogger = logging.getLogger(__name__)\nhandler = RotatingFileHandler('log_file.log', maxBytes=1000, backupCount=5)\nlogger.addHandler(handler)\n<\/pre>\n\n\n\n<ul><li>Use correct log levels!<\/li><li>Logutils package ( https:\/\/pypi.org\/project\/logutils\/ ) contains useful new and improved handlers<\/li><\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">Use Django logging alternatives?<\/h2>\n\n\n\n<p>The logging module of the standard pyhon implementation has been tested and brought to perfection.<\/p>\n\n\n\n<p>For each new version of Python, there is a possibility that each &#8220;third party module&#8221; breaks, and thus the logging in your application does not work.<\/p>\n\n\n\n<p>I would not recommend using anything other than the above module for the pure reason that the alternatives are practically the same.<\/p>\n\n\n\n<p>Don&#8217;t invent the wheel if it&#8217;s already invented. \ud83d\ude42<\/p>\n\n\n\n<p><\/p>\n\n\n\n<p><strong>Django projects with logging and analysis tools hide great power &#8211; so don\u2019t be afraid to use it to improve your application!<\/strong><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Django logging is one of few basic Django concepts that developers usually neglect but is important to master. So what &#8230; <\/p>\n<p class=\"read-more-container\"><a title=\"Introduction to Django logging with Best Practices\" class=\"read-more button\" href=\"https:\/\/zerotobyte.com\/introduction-to-django-logging-with-best-practices\/#more-155\" aria-label=\"More on Introduction to Django logging with Best Practices\">Read more<\/a><\/p>\n","protected":false},"author":2,"featured_media":542,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[7],"tags":[8,10],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v20.4 - https:\/\/yoast.com\/wordpress\/plugins\/seo\/ -->\n<title>Introduction to Django logging with Best Practices - ZeroToByte<\/title>\n<meta name=\"description\" content=\"Learn what is logging and how it works in Django, one of the most popular Python frameworks for creating web applications.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/zerotobyte.com\/introduction-to-django-logging-with-best-practices\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Introduction to Django logging with Best Practices - ZeroToByte\" \/>\n<meta property=\"og:description\" content=\"Learn what is logging and how it works in Django, one of the most popular Python frameworks for creating web applications.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/zerotobyte.com\/introduction-to-django-logging-with-best-practices\/\" \/>\n<meta property=\"og:site_name\" content=\"ZeroToByte\" \/>\n<meta property=\"article:published_time\" content=\"2021-12-02T00:00:22+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2021-12-20T15:05:13+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/zerotobyte.com\/wp-content\/uploads\/2021\/12\/django-logging-featured-image.webp\" \/>\n\t<meta property=\"og:image:width\" content=\"800\" \/>\n\t<meta property=\"og:image:height\" content=\"547\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/webp\" \/>\n<meta name=\"author\" content=\"Manuel Matosevic\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Manuel Matosevic\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"7 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/zerotobyte.com\/introduction-to-django-logging-with-best-practices\/\",\"url\":\"https:\/\/zerotobyte.com\/introduction-to-django-logging-with-best-practices\/\",\"name\":\"Introduction to Django logging with Best Practices - ZeroToByte\",\"isPartOf\":{\"@id\":\"https:\/\/zerotobyte.com\/#website\"},\"datePublished\":\"2021-12-02T00:00:22+00:00\",\"dateModified\":\"2021-12-20T15:05:13+00:00\",\"author\":{\"@id\":\"https:\/\/zerotobyte.com\/#\/schema\/person\/1ff5aa0c2aabf4491b171a0aee7874a3\"},\"description\":\"Learn what is logging and how it works in Django, one of the most popular Python frameworks for creating web applications.\",\"breadcrumb\":{\"@id\":\"https:\/\/zerotobyte.com\/introduction-to-django-logging-with-best-practices\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/zerotobyte.com\/introduction-to-django-logging-with-best-practices\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/zerotobyte.com\/introduction-to-django-logging-with-best-practices\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/zerotobyte.com\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Introduction to Django logging with Best Practices\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/zerotobyte.com\/#website\",\"url\":\"https:\/\/zerotobyte.com\/\",\"name\":\"ZeroToByte\",\"description\":\"Become a Better Dev!\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/zerotobyte.com\/?s={search_term_string}\"},\"query-input\":\"required name=search_term_string\"}],\"inLanguage\":\"en-US\"},{\"@type\":\"Person\",\"@id\":\"https:\/\/zerotobyte.com\/#\/schema\/person\/1ff5aa0c2aabf4491b171a0aee7874a3\",\"name\":\"Manuel Matosevic\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/zerotobyte.com\/#\/schema\/person\/image\/\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/e1b521f2dc00628f06c0cc77451013b6?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/e1b521f2dc00628f06c0cc77451013b6?s=96&d=mm&r=g\",\"caption\":\"Manuel Matosevic\"},\"sameAs\":[\"http:\/\/zerotobyte.com\"],\"url\":\"https:\/\/zerotobyte.com\/author\/manuelmatosevic\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Introduction to Django logging with Best Practices - ZeroToByte","description":"Learn what is logging and how it works in Django, one of the most popular Python frameworks for creating web applications.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/zerotobyte.com\/introduction-to-django-logging-with-best-practices\/","og_locale":"en_US","og_type":"article","og_title":"Introduction to Django logging with Best Practices - ZeroToByte","og_description":"Learn what is logging and how it works in Django, one of the most popular Python frameworks for creating web applications.","og_url":"https:\/\/zerotobyte.com\/introduction-to-django-logging-with-best-practices\/","og_site_name":"ZeroToByte","article_published_time":"2021-12-02T00:00:22+00:00","article_modified_time":"2021-12-20T15:05:13+00:00","og_image":[{"width":800,"height":547,"url":"https:\/\/zerotobyte.com\/wp-content\/uploads\/2021\/12\/django-logging-featured-image.webp","type":"image\/webp"}],"author":"Manuel Matosevic","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Manuel Matosevic","Est. reading time":"7 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/zerotobyte.com\/introduction-to-django-logging-with-best-practices\/","url":"https:\/\/zerotobyte.com\/introduction-to-django-logging-with-best-practices\/","name":"Introduction to Django logging with Best Practices - ZeroToByte","isPartOf":{"@id":"https:\/\/zerotobyte.com\/#website"},"datePublished":"2021-12-02T00:00:22+00:00","dateModified":"2021-12-20T15:05:13+00:00","author":{"@id":"https:\/\/zerotobyte.com\/#\/schema\/person\/1ff5aa0c2aabf4491b171a0aee7874a3"},"description":"Learn what is logging and how it works in Django, one of the most popular Python frameworks for creating web applications.","breadcrumb":{"@id":"https:\/\/zerotobyte.com\/introduction-to-django-logging-with-best-practices\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/zerotobyte.com\/introduction-to-django-logging-with-best-practices\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/zerotobyte.com\/introduction-to-django-logging-with-best-practices\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/zerotobyte.com\/"},{"@type":"ListItem","position":2,"name":"Introduction to Django logging with Best Practices"}]},{"@type":"WebSite","@id":"https:\/\/zerotobyte.com\/#website","url":"https:\/\/zerotobyte.com\/","name":"ZeroToByte","description":"Become a Better Dev!","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/zerotobyte.com\/?s={search_term_string}"},"query-input":"required name=search_term_string"}],"inLanguage":"en-US"},{"@type":"Person","@id":"https:\/\/zerotobyte.com\/#\/schema\/person\/1ff5aa0c2aabf4491b171a0aee7874a3","name":"Manuel Matosevic","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/zerotobyte.com\/#\/schema\/person\/image\/","url":"https:\/\/secure.gravatar.com\/avatar\/e1b521f2dc00628f06c0cc77451013b6?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/e1b521f2dc00628f06c0cc77451013b6?s=96&d=mm&r=g","caption":"Manuel Matosevic"},"sameAs":["http:\/\/zerotobyte.com"],"url":"https:\/\/zerotobyte.com\/author\/manuelmatosevic\/"}]}},"_links":{"self":[{"href":"https:\/\/zerotobyte.com\/wp-json\/wp\/v2\/posts\/155"}],"collection":[{"href":"https:\/\/zerotobyte.com\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/zerotobyte.com\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/zerotobyte.com\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/zerotobyte.com\/wp-json\/wp\/v2\/comments?post=155"}],"version-history":[{"count":33,"href":"https:\/\/zerotobyte.com\/wp-json\/wp\/v2\/posts\/155\/revisions"}],"predecessor-version":[{"id":317,"href":"https:\/\/zerotobyte.com\/wp-json\/wp\/v2\/posts\/155\/revisions\/317"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/zerotobyte.com\/wp-json\/wp\/v2\/media\/542"}],"wp:attachment":[{"href":"https:\/\/zerotobyte.com\/wp-json\/wp\/v2\/media?parent=155"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/zerotobyte.com\/wp-json\/wp\/v2\/categories?post=155"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/zerotobyte.com\/wp-json\/wp\/v2\/tags?post=155"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}