[Improvement] No GUI mapping for internal instance IDs shown in logs, making it impossible to identify/remove the failing torrent instance

[dsxcsman]

Summary

Rustatio logs tracker errors with internal instance IDs such as Instance p-J1BQbiws, but the GUI does not expose any matching identifier or obvious way to map that ID to the corresponding torrent/session.

This makes it very difficult to identify and remove the failing instance.

Version

Rustatio v2.5.0

Environment

• Docker
• Web UI
• Multiple active torrent instances

Reproduction

1. Run Rustatio with multiple torrent instances.
2. Let one instance hit a tracker error.
3. Check the logs.
4. Try to identify in the GUI which torrent/session matches the logged instance ID.

Example logs

[Instance p-J1BQbiws] Tracker returned failure: Torrent not registered with this tracker
[Instance p-J1BQbiws] Periodic announce failed, will retry next cycle

Actual behavior

The logs show only an opaque internal instance ID, and the GUI does not provide a way to map that ID to the affected torrent/session.

Expected behavior

Rustatio should make the failing instance identifiable, for example by:

• showing the same instance ID in the GUI, or
• including a human-readable identifier in logs such as torrent name, info hash, or tracker hostname

Why this is a problem

When a broken instance keeps retrying, there is no practical way to know which item should be stopped or removed from the UI.

Suggested improvement

Include both the internal ID and a readable identifier in logs and/or expose the instance ID in the GUI.

Example:

[Instance p-J1BQbiws | Torrent: Example.Name.S01E01 | Tracker: tracker.example.org] Tracker returned failure