Conversation
Coherent connection and flow examples; open base objects so generators can extend them; sampled_at on traffic; src and connection_id filters; GroupSummary.config_revision; probe queue-full 503 with Retry-After; health identity carries measurement; decision-time names in selection paths; CORS, datapath and cursor rules stated once.
Example timestamps fall after instance start; the preflight rule is stated in api-config and common; health identity keeps warmth; wording.
chain, rule, ingress and domain source with provenance on Connection and FlowSummary; GET /runtime/outbounds; bounded GET /runtime/traffic/history; no-close and out-of-scope statements.
ErrorCode enum on HTTP error bodies (ApiError); errors embedded in resources keep adapter-defined codes; /events 409 names event_cursor_expired and carries an example.
GET /api/v1/logs streams sanitised engine log records over SSE with
the events cursor rules; GET /api/v1/providers, GET /providers/{id}
and POST /providers/{id}/refresh (202) expose subscriptions, with
Node.provider_id; GET /api/v1/rules lists the running generation's
rules with the ids routing trace and flows use. Eight tests.
GET and PATCH /logs/settings: the level the engine emits at and the replay ring size, changeable at runtime under control when resources.logs.settings is true. A change applies without a reload and is not written to the configuration; restart or the next activation returns to the configured values, which `source` reports. Level is bounded by the advertised levels, the ring by [64, max_buffered_records]; out of range is 400 with nothing changed. logs.md gains a table of every retained record, its bound and whether it is adjustable at runtime; honk mapping row; one test.
Zakkaus
force-pushed
the
observability-endpoints
branch
from
September 16, 2026 16:23
7ec2b3d to
43afe37
Compare
GET /dns/log: the engine records each resolution it performs for clients (not diagnostic /dns/query calls) into a ring of at most resources.dns_log.max_records; newest first, filters by name substring, record type and client source IP, cursor paging within max_page_size. A record carries the client socket address (IPv6 in brackets), the question, RCODE or engine outcome, whether the cache answered, the upstream, the routing decision in the /dns/query shape, elapsed time and the answers. Not durable; clears on restart. Doc section on the DNS cache page, honk mapping row, one test.
GET and PATCH /runtime/settings replace /logs/settings: the log level and replay ring, the DNS log ring and flow retention in one place, each bounded by the matching capability value as its ceiling. resources.runtime_settings.fields lists what a backend lets a PATCH change; anything else is 400. A change applies without a reload, is not written to the configuration, and the next activation or a restart resets it; source reports which is in effect. The retention table on the logs page now says which rings are adjustable. One test.
POST /providers and DELETE /providers/{id} add and remove subscription
providers in the managed main source; POST /nodes and DELETE /nodes/{id}
do the same for inline nodes from share links. GET /geodata reports the
loaded geosite and geoip files and POST /geodata/update queues a
geodata_update operation that downloads, verifies and reloads them.
Capabilities gain providers.can_manage, nodes.can_manage and a geodata
resource; discovery links geodata. Also names the body example the
runtime settings page renders.
Zakkaus
force-pushed
the
observability-endpoints
branch
from
September 17, 2026 09:24
3992801 to
f31f6c6
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Three read-side additions the doona UI needs, stacked on #4 (
ui-findings); independent of #5.GET /api/v1/logs: SSEevent: logrecords{ts, level, target, message, fields}withlevel/targetfilters and the same cursor rules as/events(stream.ready,Last-Event-ID, 409event_cursor_expired). Messages are sanitised.GET /api/v1/providers,GET /providers/{id},POST /providers/{id}/refresh(202 operationprovider_refresh);Node.provider_id(nullable) for grouping.GET /api/v1/rules: the running generation's rules withrule_ididentical to whatPOST /routing/traceandFlowSummary.rule_iduse; refetch ongeneration.changed. Editing goes through the configuration sources (docs: effective configuration and dry-run validation #5), not a rule-level write.resources.logs,resources.providers,resources.rules; discovery links; docs pages; eight tests.Second and fourth commits, runtime settings and retention:
GET/PATCH /api/v1/runtime/settings: the log level and replay ring, the DNS log ring and flow retention in one place, each bounded by the matching capability value;resources.runtime_settings.fieldslists what a backend lets a PATCH change. Applies without a reload, is not written to the configuration file; restart or the next activation returns to the configured values andsourcesays which is in effect. Out of range is 400 with nothing changed.logs.mdgets a table of every retained record (logs, DNS log, flows, traffic and memory samples, operations), its ceiling and whether it is adjustable at runtime.Third commit, DNS log:
GET /api/v1/dns/log: a bounded ring of the resolutions the engine performed for clients (diagnostic/dns/querycalls excluded), newest first, filtered by name substring, record type and client source IP, cursor paging withindns_log.max_page_size. Each record: client socket address (IPv6 in brackets), question, RCODE or engine outcome, cache hit or upstream, routing decision in the/dns/queryshape, elapsed time, answers. Not durable.npm run check:contract: 40 pass.