# Add a verbose mode (Logs) to Gladys

**URL:** <https://community.gladysassistant.com/t/ajouter-un-mode-verbeux-logs-a-gladys/8625>\
**Category:** Demande de fonctionnalités\
**Tags:** logs, feature-core\
**Created:** [December 15, 2023, 11:58am UTC](https://community.gladysassistant.com/t/ajouter-un-mode-verbeux-logs-a-gladys/8625 "2023-12-15T11:58:30Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![cce66](https://gladys-assistant-community.b-cdn.net/letter_avatar_proxy/v4/letter/c/8797f3/32.png) [@cce66](https://community.gladysassistant.com/u/cce66)\
**Post date:** [December 15, 2023, 11:58am UTC](https://community.gladysassistant.com/t/ajouter-un-mode-verbeux-logs-a-gladys/8625/1 "2023-12-15T11:58:30Z")

</div>

I think Gladys is missing a verbose mode

Would it be possible to add a «&nbsp;Logs&nbsp;» field between «&nbsp;Service&nbsp;» and «&nbsp;System&nbsp;»?  
We could put interesting events for the user there such as:

```
Timestamp- Gladys : Update/restart
Timestamp- Containers : Update/restart
Timestamp- Scene : Start/end at step
Timestamp- Devices (lights/switches) : off/on
Timestamp- Alarm : off/on, wrong code entered, etc
Timestamp- Network loss

```

 ![image](https://gladys-assistant-community.b-cdn.net/uploads/default/original/2X/9/965727fd2967857dffd553f98afdea69410aa011.png)

To avoid this causing a large overload, it might be possible

---

<div class="post-metadata">

**Author:** ![lmilcent](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/lmilcent/32/7023_2.png) [@lmilcent](https://community.gladysassistant.com/u/lmilcent)\
**Post date:** [December 15, 2023, 12:16pm UTC](https://community.gladysassistant.com/t/ajouter-un-mode-verbeux-logs-a-gladys/8625/2 "2023-12-15T12:16:29Z")

</div>

To avoid overconsumption, could verbose mode be temporary?

«&nbsp;Activate for XX minutes&nbsp;»

---

<div class="post-metadata">

**Author:** ![pierre-gilles](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/pierre-gilles/32/5886_2.png) [@pierre-gilles](https://community.gladysassistant.com/u/pierre-gilles)\
**Post date:** [December 15, 2023, 12:19pm UTC](https://community.gladysassistant.com/t/ajouter-un-mode-verbeux-logs-a-gladys/8625/3 "2023-12-15T12:19:39Z")

</div>

@cce66 I deleted your message in the other post since it didn’t have a link 🙂

I agree there’s a problem, but I think we can implement the solution differently.

The «&nbsp;Background tasks&nbsp;» tab already exists.

That tab is indeed missing some data:

- Restarting Gladys
- Running a scene

For devices, there’s already a request:

> [@Journal d'évènements](https://community.gladysassistant.com/t/journal-devenements/8347):
>
> Feature description Ajouter un journal d’événements pour visualiser tous les états des différents appareils à travers le temps. Un exemple dans l’application freebox du pack sécurité:

---

<div class="post-metadata">

**Author:** ![cce66](https://gladys-assistant-community.b-cdn.net/letter_avatar_proxy/v4/letter/c/8797f3/32.png) [@cce66](https://community.gladysassistant.com/u/cce66)\
**Post date:** [December 15, 2023, 12:53pm UTC](https://community.gladysassistant.com/t/ajouter-un-mode-verbeux-logs-a-gladys/8625/4 "2023-12-15T12:53:27Z")

</div>

> [@pierre-gilles](#):
>
> @cce66 I deleted your message in the other post since it wasn’t related 🙂

👍

> [@pierre-gilles](#):
>
> The «&nbsp;Background Tasks&nbsp;» tab already exists.

Indeed that could work if the events mentioned above were integrated into that tab, but it should be possible to filter by events and date because it would quickly become hard to find a specific event

> [@pierre-gilles](#):
>
> For devices, there is already a request:

Indeed, I think we should ultimately merge these two requests, I may add my request as well

The ideal for me:

- a place where we can check the general state of the system (backend: updates, stop/restart containers, network status, key status, data aggregation…)
- a place where we can check the status of user-facing features (frontend: scenes, devices to see device state changes during scene execution, etc)  
Currently, you can design scenes but you almost have to verify them live to be sure they’re OK

> [@lmilcent](#):
>
> To avoid overconsumption, could verbose mode be temporary otherwise?  
> «&nbsp;Enable for XX minutes&nbsp;»

Indeed, or a FIFO log for 24 or 48 hours or based on a size allocated to logs

@pierre-gilles, if you want you can attach this post to the other one and delete this one which is more of a complement than a new request

---

<div class="post-metadata">

**Author:** ![pierre-gilles](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/pierre-gilles/32/5886_2.png) [@pierre-gilles](https://community.gladysassistant.com/u/pierre-gilles)\
**Post date:** [December 15, 2023, 1:38pm UTC](https://community.gladysassistant.com/t/ajouter-un-mode-verbeux-logs-a-gladys/8625/5 "2023-12-15T13:38:23Z")

</div>

> [@cce66](#):
>
> Indeed, I think we should ultimately combine these two requests into one; I might add my own request.

On the contrary, I prefer to have very specific requests rather than a single very vague, «&nbsp;catch-all&nbsp;» request 🙂
