Logging System

TelemetryTV offers a comprehensive logging system that provides users with various ways to access and analyze logs:

TelemetryTV Interface - Logs Tab (Aggregated View)

This tab serves as a centralized log aggregation point where you can view logs from all devices connected to the TelemetryTV network.
It's useful for getting an overview of the system's health and for spotting widespread issues that might be affecting multiple devices.
You can typically filter these logs by severity, search by device, time, and possibly other criteria to quickly find the information you need.

Click here for more information on reporting an issue.

Device Log Detail

Severity - The severity level of the error log. From lowest severity to highest: Debug, Info, Alert/Warning, or Error.
Component - The affected area of the device producing the error.
Code - The specific error code produced, usually accompanied with a message detailing the error.
Message - A detailed message explaining the error.
Time - Time and Date of the logged error.
Device ID - The device ID number that produced the error.
Device Name - The name of the device that produced the error.

Logs from a device

Device Logs

Account Logs

Device Debug Console

Debug Console

Initial Steps

1-Check the Logs Immediately

As soon as an unexpected behavior is noticed, the first step should always be to check the logs. This is because logs can provide real-time insights into what the application is doing behind the scenes.

2-Identify Log Severity

Logs come with different severity Debug, Info, Warning, Error, and Critical. Pay special attention to Error and Critical logs, as these are most likely pertain to unexpected behaviors.

3-Look for Exception Messages

Exception messages in logs are deliberately placed by developers to highlight where an issue has occurred. These exceptions often include a stack trace or error message that can pinpoint the exact location in the code where the behavior deviated from the expected path.

Unhandled Errors

Unhandled errors are those that were not explicitly caught by the application's error handling routines. These are critical because they can indicate edge cases or unforeseen scenarios that were not accounted for during development.

4-Analyzing Logs

Filter and Search

Use the filtering and search functionalities within the TelemetryTV interface to isolate logs from around the time the issue was first observed.

Correlate Events

Try to correlate the unexpected behavior with specific log entries. Look for patterns or repeated errors that coincide with the issues you're observing.

Note Timestamps

Document the timestamps of relevant logs. This information will be crucial when you need to communicate the details to the support team through our Support icon.

Gather Context

If possible, gather context around the error, such as what the application was doing at the time, any user interactions that occurred, and the state of the system.