CRATEFIELD
Get started with Harness Join the waitlist

telemetry

Counted, aggregate usage telemetry with consent built in, and no stored link to a person.

With fz, into the venture manifest

fz add telemetry

With cargo

cargo add cratefield-module-telemetry

fz runs inside your venture repository, linked against its own harness. About fz

crates.iodocs.rsSource

What it is

telemetry.

Aggregate usage telemetry for a Cratefield venture: clients report batches of counted events to POST /v1/telemetry/events, every field is validated against a closed grammar — an unknown field or an undeclared value is a rejection, never a truncation — and the counts accumulate into buckets in the venture's own database. No third-party analytics service, no vendor SDK, and no field anywhere a sentence could fit.

From the crate’s own README.

Read more

History

Changelog.

From the crate’s CHANGELOG.md in the harness, as of 0c5560b. 4 versions recorded, newest first. Every published version is on crates.io.

  1. 0.3.2

    crates.ioReleaseDiff

    Other

    • updated the following local packages: cratefield-core

  2. 0.3.1

    crates.ioReleaseDiff

    Other

    • updated the following local packages: cratefield-core
2 earlier versions 0.2.1 to 0.3.0

  1. 0.3.0

    crates.ioReleaseDiff

    Changed

    • Breaking: requires cratefield-core 0.8 (was 0.7), and so a minor rather than a patch bump: a venture still on core 0.7 does not pick this release up through a caret requirement and end up with two copies of core (#712).

    Other

    • updated the following local packages: cratefield-core

  2. 0.2.1

    crates.ioRelease

    Other

    • updated the following local packages: cratefield-core

One of 76 crates in the harness, all of them MIT and all of them in one repository.

Join the waitlist All modules