Host: docker2 — Monitoring Central (jakemon) and CrafterCMS

Role: the central observability host plus the CrafterCMS web platform. LAN address 192.168.0.5 (JAKEMON_CENTRAL_ADDR). Every fleet host pushes metrics and logs here via Grafana Alloy agents.

Stale-docs warning: jakemon's README and .env.example still describe the central stack as running on inference (192.168.0.10). That host was decommissioned in July 2026; remote.env (JAKEMON_CENTRAL=docker2) is the truth. Trust this page and remote.env, not the README.

What runs here — jakemon central stack

ServicePortAccess
Prometheus9090Open on the LAN — query webmaster_*, node, container metrics directly; no auth
Grafana3000Auth required (GRAFANA_ADMIN_PASSWORD in jakemon .env); dashboards provisioned from the repo
Loki3100Log store; queried through Grafana
Alertmanager127.0.0.1:9093Loopback-only
cf-analytics-exporterCloudflare analytics → Prometheus
visibility-exporterSearch-engine webmaster data → Prometheus; see Search Visibility Exporter

Agent tip: for dashboard data, skip the Grafana UI/API (needs auth) and query Prometheus directly — http://docker2:9090/api/v1/query — with the PromQL you can read out of the dashboard JSON in jakemon/dashboards/. Fleet metrics carry a host label — check it before diagnosing prod from a metric; docker1 and docker2 both emit wikantik_*-style series when instances exist on each.

What runs here — CrafterCMS platform

The delivery stack behind jakefear.com and maiiavorobiova.com (two vhosts, one Engine, selected by Host header):

ServicePortPurpose
crafter-proxy (nginx)8082Delivery proxy fronting both vhosts
crafter-delivery / crafter-delivery-greenDelivery Engine (blue/green pair)
authoring-tomcat8084Crafter Studio authoring
crafter-deployer / authoring-deployer9191/9192Deployers
OpenSearch ×29202 (authoring)Search for authoring + delivery
crafter-exporter172.17.0.1:9209Prometheus metrics from the Crafter monitoring APIs

Monitoring for this stack: the craftercms-platform / craftercms-traffic dashboards, plus per-vhost blackbox probes through the proxy (see jakemon/hosts/docker2/apps.alloy).

History

An old CI/CD wikantik test instance (compose project repo, port 8080, with its own pgvector DB) ran here until 2026-08-08; it and its Alloy scrape block were removed. Leftover inert files may remain under ~/wikantik/ on the host.

How it is managed

From the jakemon repo: bin/validate.sh (config check), bin/deploy-central.sh (the central stack), bin/deploy-agent.sh <host> (per-host Alloy agent), bin/deploy-crafter-exporter.sh (the Crafter exporter). The canonical host list is JAKEMON_HOSTS in remote.env; per-host app scrape targets live in hosts/<host>/apps.alloy.

See Also