Gate Connection/Call Log

[polklabs]

Enhancement Idea

Currently we have the logs/milkyway.log which has all logs. And we have dialing_log.json which just has established counts and minutes.

Add a connection/call log that can be accessed from the web UI.

• Integrated into dialing_log.py which already has the needed info
• Store X number of calls (256?)
• Use key for incoming vs outgoing. Or have 2 separate arrays?

Possible data format:

[
  {
    "activity": "outbound",
    "name": "ABYDOS" // In case gate is removed from address book
    "address": [ 27, 7, 15, 32, 12, 30 ],
    "type": "standard",
    "start_time": "2025-07-23T19:45:32.123Z", // UTC format or Epoch time,
    "elapsed": 5.32, // minutes
  },
  {
    "activity": "inbound",
    "name": "Kristian Tysse"
    "address": [ 7, 5, 20, 27, 32, 21 ],
    "type": "fan",
    "start_time": "2025-07-30T12:34:56.928Z",
    "elapsed": 25.3,
  },
]

[jonnerd154]

I like this idea - thanks for bringing it up.

One recommendation, but not a huge deal one way or the other: I'm a fan of leaving immutable and easily-calculable attributes out of disk-written data structures. The amount of compute required to parse the date strings to DateTime objects and calculate elapsed are negligible, and parsing it to a DateTime allows for other operations on that data - sorting, filtering, etc.

Perhaps this structure?

activity --> ENUM("inbound", "outbound")
success --> Boolean
name --> String(100) # Gate name, in case it's removed from the address book
address --> Array(Int)[9]
type --> ENUM("standard", "fan")
start_time --> String(20) # Encoded as ISO 8601, Zulu/UTC
end_time --> String(20) # Encoded as ISO 8601, Zulu/UTC