Connections / Data and dashboards
Grafana dashboards and Marrow Health
Automated
Your health data on Grafana dashboards: Marrow posts to InfluxDB on a schedule and Grafana charts it.
Open in Marrow works on an iPhone with Marrow 1.4.2 or later.
Automated (Dashboards from InfluxDB) Free
Marrow posts CSV or JSON to a URL on a schedule, with the app closed. You need: Telegraf or the 30-line bridge from the recipe.
- In Marrow, open Export and tap Grafana dashboards. Turn Automated on.
- Run the Telegraf listener or the bridge from the recipe in front of InfluxDB.
- In Marrow: New Automation. Its page asks for:
- Address: The address of the bridge or Telegraf listener, not InfluxDB itself. It looks like
https://<bridge>/. - Headers: Add Authorization: Bearer and the secret the bridge expects.
- Data and Cadence: the kind of data, JSON or CSV, and how often it runs.
- Run: Tap Run now. Then point a Grafana dashboard at the InfluxDB bucket.
- Address: The address of the bridge or Telegraf listener, not InfluxDB itself. It looks like
If it does not work
In Grafana dashboards
- Marrow posts straight to InfluxDB and fails. InfluxDB's write API takes line protocol only, so Marrow's JSON gets a 400. Point Marrow at the bridge or the Telegraf listener from the recipe.
- Server answered 502. The recipe's bridge answers 502 when InfluxDB refused the write. Check the org and bucket in
INFLUX_URLand the token inINFLUX_AUTH. - Server answered 401. The secret in Marrow's Authorization header does not match
MARROW_SECRETon the bridge, or the Basic auth on the Telegraf listener. - The dashboard is empty. Each day is stored at midnight UTC, so set the time range to the last 30 days or more. The query languages Grafana offers depend on the InfluxDB version, and Flux is not on InfluxDB 3.
Automated checks
- Test with Run now. The line under Run now says what happened. Any 2xx answer counts as delivered. Anything else shows as Server answered and the status code, or the network error.
- Check the Activity log. In the automation, More options, Activity log lists its last 30 runs with the result of each.
- Runs come late. iOS picks the moment for background runs, and a phone that stays locked sends when it is next unlocked. Since last run catches up on the next run that succeeds.
- A receiver on your home network. Marrow needs Local Network access to reach it (Settings, Privacy and Security, Local Network). Tap Run now once with Marrow open, so iOS can ask: in the background it refuses without asking.
- It will not switch on. Each automation that is on counts as a connection. Free keeps 1 connection on at a time. Marrow Pro keeps up to 10: AIs, servers and automations together.
More fixes in the guides: Automated.