Probe Logs

Purpose

This page is used to review temperature readings and event history from probes so teams can verify conditions and investigate anomalies.

Prerequisites

• Probes/devices must be active and reporting data.
• Devices should be assigned to valid locations.
• Users need permission to view telemetry or logs.

Main Actions

• View recent and historical probe readings.
• Filter by time range, location, or device.
• Identify spikes, dropouts, or unusual patterns.
• Use log context to support follow-up actions.

Field/Status Reference

• Reading Value: Captured temperature at a specific time.
• Recorded At: Timestamp of the reading.
• Device/Probe: Source hardware for the data point.
• Location: Physical area where the device is assigned.
• Signal/Health Indicators: Availability or reliability context for data quality.

Workflow

1. Open logs for the relevant date range.
2. Narrow results by location/device if needed.
3. Review trends and outlier points.
4. Validate whether anomalies are real or sensor-related.
5. Escalate to alerts or corrective action when required.

Connections

• Supports decision-making in Alerts and Corrective Actions.
• Depends on proper setup in Devices and Locations.
• Feeds incident reviews where detailed timelines are required.

Common Mistakes

• Reviewing too broad a date range and missing local patterns.
• Ignoring location context when comparing readings.
• Assuming missing data is safe data.

Troubleshooting

• If logs are empty, confirm the device is online and assigned.
• If readings seem wrong, verify calibration and recent maintenance.
• If timestamps look inconsistent, check timezone and sync status.

Quick Tips

• Start with a short timeframe, then expand only if needed.
• Compare multiple probes in the same area to confirm anomalies.
• Keep notes on suspected sensor faults for maintenance follow-up.