Automatic Events Log analyser - for observations & troubleshooting #2786
Replies: 1 comment 8 replies
-
There is a reasonable expectation that if a developer modifies a part of the code, they would accordingly edit the including logs that re affected. But, if we create the capability for the logs to be interpreted, we will need an additional program or function. Such a function or program will need to be maintained. What happens when a developer modifies a feature in xDrip? Whose responsibility will it be to update the interpreter? Have you thought about that? |
Beta Was this translation helpful? Give feedback.
-
Has there been any consideration to building into xDrip+ the facility to analyse the events log. As xDrip has more features, the number & different entries in the log can be somewhat intimidating, and can sometime lead to repeated questions, with only partial information provided. Not all users will understand the significance of the information in the log, and the sheer volume of data can overwhelm, unless one knows precisely what to look for.
Perhaps the first stage would be to have the tool provide some simple observations, such as:
And the next stage could be t provide some diagnostics, or interpretations/conclusions:
Having recently switched from Libre1 + bridge, to bridgeless Libre2, there is a lot of new information in the log, and I have found it rather like looking for a needle in a haystack, and have ended up asking dumb questions to the forum.
I am not aware of any section of the documentation dedicated to "How to understand the Event Logs" - but maybe creating this would be a useful precursor to any automation of the analysis.
Apologies if this has been discussed before.
Beta Was this translation helpful? Give feedback.
All reactions