From 1f6d38af1687d768368c2757ea2a461611c6f5d9 Mon Sep 17 00:00:00 2001
From: hkonsti <45428767+hkonsti@users.noreply.github.com>
Date: Fri, 6 Nov 2026 00:33:07 +0000
Subject: [PATCH] write the loki's and the prometheus's addresses into the
 blueprint, as the sandbox service's is

Render gave them their names; a Blueprint fills in only its own services' addresses, and a
dashboard-set value that a sync turned over from a fixed one went empty, so the api shipped
nothing. Written here, they can't; a service made anew in Render gets a new suffix, which the
comment says has to follow.
---
 render.yaml | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/render.yaml b/render.yaml
index b1b500fe..36d76b34 100644
--- a/render.yaml
+++ b/render.yaml
@@ -85,14 +85,14 @@ services:
       - key: TELEMETRY_ENABLED
         value: 'false'
       # Where the log and the metrics go: the Loki and the Prometheus the internal repo
-      # (personalagentproxy/internal) runs beside this service, each by the address Render gives
-      # it on the private network, `host:port` with no scheme, such as `loki-ab12:3100`, shown
-      # under the service's Connect menu; neither takes auth. A Blueprint only fills in its own
-      # services' addresses, so these are set by hand. Unset, the log stays on stdout.
+      # (personalagentproxy/internal) runs beside this service, each by the address Render gave it
+      # on the private network, `host:port` with no scheme, as the sandbox service above; neither
+      # takes auth. A Blueprint only fills in its own services' addresses, so these are written
+      # here: a service made anew in Render gets a new suffix, and its address here has to follow.
       - key: LOKI_URL
-        sync: false
+        value: loki-6lgn:3100
       - key: METRICS_OTLP_URL
-        sync: false
+        value: prometheus-zk70:9090
       # Where sign-ups are posted (packages/observability/README.md); optional.
       - key: SLACK_BOT_TOKEN
         sync: false