Filtering of logs window

I use the logs a lot when figuring out logic problems, but since I have so many devices and actions, the log is full of items that are not related to what I'm debugging and scrolls by quite fast. It would be really helpful for me to be able to filter the log window (like on iphone) so the logs shown are more relevant to what I'm debugging. Also, having a timestamp as a first column would be useful in figuring out timing issues.

Agreed, and is on the list, but have you thought about opening log in a text editor?

I do when debugging issues.


Sent from my iPhone using Tapatalk Pro

/library
Application support
Perceptive automation
Indigo 7.3
Logs

From memory


Sent from my iPhone using Tapatalk Pro

Yes, I do that. But its would be more convenient to be able to do it right in the log window. Especially that my Indigo setup is on a dedicated computer on a separate secured dedicated subnet. The best way is to use tail with grep, but its just way more work to do that in my situation.

[jay (support)]

We have a boatload of ideas for log improvements. Someday...

I understand the logging isn't a top priority, but a simple filter as in indigo Touch would go a long way.

I use something like that:

Code: Select all

tail -f indigo_log.txt |grep --line-buffered "my filter string"

Works pretty well. And on top of that, you can use regex as the filter.

My favourite:

Code: Select all

tail -f indigo_log.txt |grep --line-buffered "Trigger.*L1_WC"

Which shows any Triggers for my Level 1 washroom.

Code: Select all

2019-05-25 23:37:23.805   Trigger   L1_WC_DR_Opened_VAR
2019-05-25 23:37:23.806   Trigger   L1_WC_VOCP_LT_ON
2019-05-25 23:37:23.807   Trigger   L1_WC_VOCP_ON_ACTN_VAR
2019-05-25 23:37:27.058   Trigger   L1_WC_OCP_Z_ON_VAR
2019-05-25 23:37:36.356   Trigger   L1_WC_LT_OFF
2019-05-25 23:37:36.362   Trigger   L1_WC_VOCP_LT_OFF
2019-05-25 23:37:36.364   Trigger   L1_WC_VOCP_OFF_VAR

Thats me going in and out and turning the light off.

And here the same action without filter. A lot harder to figure out what happened. And this is at night with everybody in bed (except me )

Code: Select all

2019-05-25 23:38:51.341   Z-Wave   received "L1_WC_HUMD_Z" sensor update to 46%
2019-05-25 23:38:52.355   Z-Wave   received "L1_WC_LUM_Z" sensor update to 0 lux
2019-05-25 23:38:52.684   Z-Wave   received "L1_WC_UV_Z" sensor update to 0
2019-05-25 23:38:56.622   Z-Wave   received "L1_FR_AV_TEMP_Z" sensor update to 23.9 °C
2019-05-25 23:38:56.951   Z-Wave   received "L1_FR_AV_HUMD_Z" sensor update to 44%
2019-05-25 23:38:57.485   Schedule   LogErrorFound (delayed action)
2019-05-25 23:38:57.936   Script   Status request to: L3_BR_Guest_LT
2019-05-25 23:38:58.024   Z-Wave   received "L1_FR_AV_LUM_Z" sensor update to 0 lux
2019-05-25 23:38:58.223   Sent INSTEON   "L3_BR_Guest_LT" status request (received: 0)
2019-05-25 23:38:58.311   Z-Wave   received "L1_FR_AV_UV_Z" sensor update to 0
2019-05-25 23:39:00.542   Trigger   L1_FR_MNT_ON_VAR
2019-05-25 23:39:00.542   Trigger   Occupancy Log Update
2019-05-25 23:39:00.543   DSC Alarm   Alarm Zone 'L1_FR_MTN' Opened.
2019-05-25 23:39:02.513   Trigger   L1_FR_MNT_OFF_VAR
2019-05-25 23:39:02.514   DSC Alarm   Alarm Zone 'L1_FR_MTN' Closed.
2019-05-25 23:39:03.854   Trigger   L1_FR_MNT_ON_VAR
2019-05-25 23:39:03.855   DSC Alarm   Alarm Zone 'L1_FR_MTN' Opened.
2019-05-25 23:39:04.043   Received INSTEON   "L2_HALL_OCP" off (button 1)
2019-05-25 23:39:04.044   Trigger   L2_Hall_OCP_OFF_VAR
2019-05-25 23:39:04.200   Z-Wave   received "L1_WC_DR_Z" status update is on
2019-05-25 23:39:04.201   Trigger   L1_WC_DR_Opened_VAR
2019-05-25 23:39:04.201   Trigger   L1_WC_VOCP_LT_ON
2019-05-25 23:39:04.202   Action Group   L1_WC_LT_ON
2019-05-25 23:39:04.203   Trigger   L1_WC_VOCP_ON_ACTN_VAR
2019-05-25 23:39:04.203   Trigger   Occupancy Log Update
2019-05-25 23:39:04.595   Z-Wave   device "011 - L1_WC_LT_Z" parameter 11 "Remote Ramp Rate" changed to 0 seconds
2019-05-25 23:39:04.736   Z-Wave   sent "L1_WC_LT_Z" on
2019-05-25 23:39:05.482   Schedule   L1_WC_VOCP_LT_ON (delayed action)
2019-05-25 23:39:05.894   Trigger   L1_FR_MNT_OFF_VAR
2019-05-25 23:39:05.895   DSC Alarm   Alarm Zone 'L1_FR_MTN' Closed.
2019-05-25 23:39:06.365   Trigger   L1_FR_MNT_ON_VAR
2019-05-25 23:39:06.365   Trigger   Occupancy Log Update
2019-05-25 23:39:06.366   DSC Alarm   Alarm Zone 'L1_FR_MTN' Opened.
2019-05-25 23:39:07.665   Z-Wave   received "L1_WC_OCP_Z" status update is on
2019-05-25 23:39:07.665   Trigger   L1_WC_OCP_Z_ON_VAR
2019-05-25 23:39:07.944   Script   Status request to: L3_BR_Master_CLS_1_LT
2019-05-25 23:39:08.245   Trigger   L1_FR_MNT_OFF_VAR
2019-05-25 23:39:08.246   DSC Alarm   Alarm Zone 'L1_FR_MTN' Closed.
2019-05-25 23:39:08.280   Sent INSTEON   "L3_BR_Master_CLS_1_LT" status request (received: 0)
2019-05-25 23:39:10.996   Trigger   L1_FR_MNT_ON_VAR
2019-05-25 23:39:10.997   DSC Alarm   Alarm Zone 'L1_FR_MTN' Opened.
2019-05-25 23:39:11.548   Z-Wave   received "L1_WC_DR_Z" status update is off
2019-05-25 23:39:12.977   Trigger   L1_FR_MNT_OFF_VAR
2019-05-25 23:39:12.978   DSC Alarm   Alarm Zone 'L1_FR_MTN' Closed.
2019-05-25 23:39:13.108   Z-Wave   received "L1_WC_LT_Z" off button pressed
2019-05-25 23:39:13.109   Z-Wave   received "L1_WC_LT_Z" status update is off
2019-05-25 23:39:13.110   Trigger   L1_WC_LT_OFF
2019-05-25 23:39:13.115   Trigger   L1_WC_VOCP_LT_OFF
2019-05-25 23:39:13.115   Action Group   L1_WC_LT_OFF_SLOW
2019-05-25 23:39:13.117   Trigger   L1_WC_VOCP_OFF_VAR
2019-05-25 23:39:13.572   Z-Wave   device "011 - L1_WC_LT_Z" parameter 11 "Remote Ramp Rate" changed to 10 seconds
2019-05-25 23:39:13.838   Trigger   L1_FR_MNT_ON_VAR
2019-05-25 23:39:13.839   DSC Alarm   Alarm Zone 'L1_FR_MTN' Opened.
2019-05-25 23:39:14.483   Schedule   L1_WC_VOCP_LT_OFF (delayed action)
2019-05-25 23:39:14.577   Z-Wave   sent "L1_WC_LT_Z" off
2019-05-25 23:39:15.484   Schedule   L1_WC_VOCP_LT_OFF (delayed action)
2019-05-25 23:39:15.809   Trigger   L1_FR_MNT_OFF_VAR
2019-05-25 23:39:15.810   DSC Alarm   Alarm Zone 'L1_FR_MTN' Closed.
2019-05-25 23:39:15.848   Z-Wave   device "011 - L1_WC_LT_Z" parameter 11 "Remote Ramp Rate" changed to 0 seconds
2019-05-25 23:39:17.946   Script   Status request to: L3_BR_Master_CLS_2_LT
2019-05-25 23:39:19.519   Sent INSTEON   "L3_BR_Master_CLS_2_LT" status request (received: 0)

If the log file would be named .log and not . txt console viewer would do a really nice job.


Sent from my iPhone using Tapatalk

[jay (support)]

I understand the logging isn't a top priority, but a simple filter as in indigo Touch would go a long way.

Simple as a concept, but not necessarily so in implementation complexity. There are 2 parts to prioritization: 1) importance and 2) implementation complexity.

Fully agree. If for any reason it's not trivial then its better to concentrate on other things. For now, I've opened ssh to the server and will do tail and grep from my terminal.

Woud an option to post to a remote syslog server be easier. to implement? Synology has a nice syslog server. Splunk is a great cloud based syslog server.

I've considered writing a plugin that will echo the log to a syslog server.

Great idea.

I was trying to think of a plugin solution yesterday but couldn’t come up with anything workable and user friendly.

SSH, grep and tail isn’t for your average home user, but the right syslog app could be.


Sent from my iPhone using Tapatalk Pro

Just want to make sure that there is clarity on the new feature of indigo

Each plugin has its own log file

All of mine will be much more verbose in the dedicated logfiles and only print startup end and serious error messages into the common log file.

So any solution should be aware of these extra log files.

Karl


Sent from my iPhone using Tapatalk

Woud an option to post to a remote syslog server be easier. to implement? Synology has a nice syslog server. Splunk is a great cloud based syslog server.

Splunk can either be installed locally or as a SaaS model.

Graylog is another contender; similar to Splunk but the default (free) license can index more per day.

I am really liking the addtion of a network monitoring system(NMS) to my toolkit. Has both SNMP monitoring as well as a decent syslogger. I couple the NMS/Indigo to a SLACK channel for notifcation.

I find that SLACK is my most often used UI on a day to day basis. Indigo does all the automation, NMS the monitoring and SLACK notifies if something need attention. I rarely need to open Indigo touch or the NMS UI.