From 752f1a46d166c393720c54c3dbbd7d806e9a5237 Mon Sep 17 00:00:00 2001 From: Gert Date: Sat, 25 Jan 2020 12:53:02 +0000 Subject: [PATCH] Document Recorder event_type exclude option (#11865) * Document event_type exclude option * Update source/_integrations/recorder.markdown Co-Authored-By: Franck Nijhof Co-authored-by: Franck Nijhof --- source/_integrations/recorder.markdown | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/source/_integrations/recorder.markdown b/source/_integrations/recorder.markdown index 7002f58b2789..793883fc4c65 100644 --- a/source/_integrations/recorder.markdown +++ b/source/_integrations/recorder.markdown @@ -54,6 +54,10 @@ recorder: description: The list of entity ids to be excluded from recordings. required: false type: list + event_types: + description: The list of event types to be excluded from recordings. + required: false + type: list include: description: Configure which integrations should be included in recordings. If set, all other entities will not be recorded. required: false @@ -85,6 +89,8 @@ recorder: - sun.sun # Don't record sun data - sensor.last_boot # Comes from 'systemmonitor' sensor platform - sensor.date + event_types: + - call_service # Don't record service calls ``` define domains and entities to record by using the `include` configuration (aka. whitelist) is convenient if you have a lot of entities in your system and your `exclude` lists possibly get very large, so it might be better just to define the entities or domains to record.