Overview
Logs tell you what happened. During an incident the question is usually narrower: what is this client, and what did we do about it. The agent already captured the answer, one local socket away.
EventBridge is that socket: a control socket for request and response queries about a connection, and an event socket that streams fingerprints as they arrive. Both are local only, with no network listener to secure.
When you see this
- An alert names an address and you need to know what client is behind it.
- Your application wants the client's TLS fingerprint, SNI or ALPN, which it cannot see itself.
- A deployment needs a quick check that the agent is seeing traffic.
Steps
- 01
Attach the live view
Standalone mode attaches a viewer to the running agent over a local socket and detaches again, leaving the agent untouched.
Attach to the running daemon synapse --terminal - 02
Open the sockets
Both sockets are off until you give them a path. Restart after setting them. On Windows they are loopback TCP instead: 127.0.0.1:19198 for control and 127.0.0.1:19199 for events.
/etc/synapse/config.yaml daemon: control_socket: "/var/run/synapse-control.sock" event_socket: "/var/run/synapse-events.sock" - 03
Ask about one connection
src_ip and src_port are required; narrow with dst_ip, dst_port, ja4 or ja4t. Only fields actually captured appear. A connection the cache has evicted returns 404 with status not_found.
EventBridge query curl --unix-socket /var/run/synapse-control.sock \ -X POST http://localhost/query \ -H 'Content-Type: application/json' \ -d '{"src_ip":"203.0.113.42","src_port":54321}' - 04
Behind CGNAT, ask by address
Set aggregate and drop src_port to get every connection seen under that address. Combine it with expect_ja4_prefix to keep only one fingerprint family.
EventBridge query curl --unix-socket /var/run/synapse-control.sock \ -X POST http://localhost/query \ -H 'Content-Type: application/json' \ -d '{"src_ip":"203.0.113.42","aggregate":true}' - 05
See what every layer decided
The event log has one record per decision, from every layer, in the same shape.
One address, across every layer jq -c 'select(.src_ip == "203.0.113.42")' /var/log/synapse/events.log - 06
Watch the stream
The event socket needs no handshake: connect, and events arrive as newline-delimited JSON. Packet events carry connection fingerprints; Http events need the proxy to have parsed a request.
Live fingerprints socat -u UNIX-CONNECT:/var/run/synapse-events.sock - \ | jq -c 'select(.type == "Packet") | {src_ip, ja4, sni}'
Common mistakes
- Expecting history. The cache is bounded and recent; use the event export for anything retrospective.
- Querying one port behind CGNAT, where many clients share the address. Use aggregate.
- Treating the terminal view as monitoring. Nobody is watching a terminal at 3am.
Escalate when
- The connection carries a fingerprint a rule or the classifier already flagged.
- The SNI the client asked for does not match the host it reached.
Where this stops working
- Local only, by design: anything off-host goes through the export path.
- Answers are best-effort. A field is absent rather than wrong when a view was never captured.