container collectors scrape their own telemetry and push it up their hop

nix/module-eval/bao-otel-collector.nix

@@ -22,6 +22,7 @@ let
     runGroup
     baoSettings
     forceServiceConfigs
+    selfScrapes
     ;
 
   baoTwoAddresses = hive {
@@ -185,6 +186,20 @@ let
         && m.exporters == [ "otlphttp" ]
         && m.exporters == s.service.pipelines.logs.exporters;
     }
+    {
+      # The store's collector reports its own health through a pipeline of its
+      # own: the store pipeline above upserts `service.name`, and sharing it
+      # would relabel these series away from the collector dashboard.
+      name = "the store's collector scrapes its own telemetry endpoint on loopback";
+      ok =
+        let
+          s = (baoForwarder baoWithCollector).settings;
+          port = baoWithCollector.services.hyperhive.swarm.bao.otel.telemetryPort;
+        in
+        selfScrapes s port { container = "bao"; }
+        && s.service.pipelines.metrics.receivers == [ "prometheus" ]
+        && s.service.pipelines.metrics.processors == [ "resource" ];
+    }
     {
       # Presence control for the case above: both fields are omitted rather
       # than defaulted, so a target declared as bare `host:port` renders what