# Logs

> Review who changed the selected network, what changed and when it happened.

Source: https://www.widewired.com/page/docs/activity-log

## Find a change

Select the network and open **Insights → Logs**. Choose the time range, filter by event type, and enter a keyword when needed. Submit the search to apply it.

Read each row's time, event, actor and target. Open a row for details. Records include device registration and approval, blocking, updates and removal, network property changes, link policies, forwarding and route changes.

These logs concern the selected network. They are not operating-system logs, application payloads or a complete history of account sign-ins. For script output, use **Configuration → Automation** and open the device's execution history.

## Investigate an unexpected change

1. Note when the symptom first appeared.
2. Search the same period for changes to the affected device, link or network.
3. Compare the event details with the current setting in Configuration or Management.
4. If correction is needed, edit the setting in its usual page and verify the result. Reading a log does not revert a change.

Compare [Quality](https://www.widewired.com/page/docs/quality), [Traffic](https://www.widewired.com/page/docs/traffic) or [Alerts](https://www.widewired.com/page/docs/alerts) for the same period. A change near the time of a fault is a lead to investigate, not proof of its cause.

## Share a useful record

For [Getting support](https://www.widewired.com/page/docs/support), provide the selected network, event time and timezone, affected object and relevant event details. Remove unrelated personal information from screenshots. Never send passwords or verification codes.

## Quick troubleshooting

| Symptom | Check and action |
| --- | --- |
| The expected event is missing | Confirm the network, time range, event-type filter and search text |
| A service problem has no configuration event | Review Quality and Alerts; a connectivity problem need not involve a setting change |
| Script output is missing | Use the device's automation execution history; Logs is not a script-output viewer |
| The current setting differs from an older event | Check later changes and inspect the current configuration before editing |