From c6ed04cf085285209bc156aa5d54103dc222c605 Mon Sep 17 00:00:00 2001 From: Rene Nulsch <33263735+ReneNulschDE@users.noreply.github.com> Date: Mon, 8 Feb 2021 11:03:33 +0100 Subject: [PATCH] Add description of name field (#16453) Add description "name" field. fixes: https://github.com/home-assistant/core/issues/45825 --- source/_integrations/system_log.markdown | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/source/_integrations/system_log.markdown b/source/_integrations/system_log.markdown index e2a42155efe..58dda10f5b2 100644 --- a/source/_integrations/system_log.markdown +++ b/source/_integrations/system_log.markdown @@ -59,6 +59,7 @@ Errors and warnings are posted as the event `system_log_event`, so it is possibl | `source` | File that triggered the error, e.g., `core.py` or `media_player/yamaha.py`. | | `exception` | Full stack trace if available, an empty string otherwise. | | `message` | Descriptive message of the error, e.g., "Error handling request". | +| `name` | Name of the component, e.g., `homeassistant.components.device_tracker` | | `timestamp` | Unix timestamp with as a double, e.g., 1517241010.237416. | Live examples of these events can be found in the Home Assistant log file (`home-assistant.log`) or by just looking in the system log. An example could, for instance, look like this: @@ -71,7 +72,7 @@ Traceback (most recent call last): [...] ``` -The message ("Unable to find integration system_healt"), source (`homeassistant.loader`) and level (`ERROR`) can easily be extracted from the log. The exact timestamp and if there is a stack trace that's shown as well. Here is another error caused by the `google_map` integration with additional output present. +The message ("Unable to find integration system_healt"), name (`homeassistant.loader`) and level (`ERROR`) can easily be extracted from the log. The exact timestamp and if there is a stack trace that's shown as well. Here is another error caused by the `google_map` integration with additional output present. ## Examples