Business and tech observability in the one product. Because this separation hurts us.

The shortest guide to run queries

jq command in the end is optional, it's for more readable output.

curl "https://app.manyevents.cloud/manage-api/v0-unstable/signin" -d '{"email": "your_email@.com", "password": "<your_password>"}' -H "Content-Type: application/json" | jq

Got response:

{
  "is_success": true,
  "auth_token": "962a235f2661439d923bdf3def535e0f7acb6890fb241822a1cd9cd47b636db5"
}

Use auth_token in Authorization: Bearer <<TOKEN>> within next queries, except push-event endpoint, which requires dedicated push_token we will receive now. Let's create own company-tenant.

curl "https://app.manyevents.cloud/manage-api/v0-unstable/create-tenant" -d '{"title": "my-company"}' -H "Content-Type: application/json" -H "Authorization: Bearer 962a235f2661439d923bdf3def535e0f7acb6890fb241822a1cd9cd47b636db5" | jq

Got response:

{
  "is_success": true,
  "id": "3f921452-33f3-4f54-b124-a313acb6922e",
  "clickhouse_read_dsn": "clickhouse://user_3f92145233f34f54b124a313acb6922e:my_password@ch.manyevents.cloud/db_3f92145233f34f54b124a313acb6922e",
  "clickhouse_admin_dsn": "",
  "push_token": "736b9beb1cfe82f53dba1204df9f4f89efb7f56c8c95a54677e6edcbaca9b034"
}

id - Created tenant id. We will use it in the following query. clickhouse_read_dsn - could be used to access database with read-only user.

Let's declare a schema for wide-event named main. In manage api we still use our first bearer token.

curl "https://app.manyevents.cloud/manage-api/v0-unstable/apply-event-schema-sync" \
-d '{"tenant_id": "3f921452-33f3-4f54-b124-a313acb6922e", "name": "main", "schema": {"type": "object",
    "properties": {
        "base_timestamp": { "type": "integer", "x-manyevents-ch-type": "DateTime64(3)" },
        "base_parent_span_id": { "type": "string", "x-manyevents-ch-type": "String" },
        "base_message": { "type": "string", "x-manyevents-ch-type": "String" },
        "span_start_time": { "type": "integer", "x-manyevents-ch-type": "DateTime64(3)" },
        "span_end_time": { "type": "integer", "x-manyevents-ch-type": "DateTime64(3)" },
        "span_id": { "type": "string", "x-manyevents-ch-type": "String" }
    },
    "x-manyevents-ch-order-by": "base_timestamp",
    "x-manyevents-ch-partition-by-func": "toYYYYMMDD",
    "x-manyevents-ch-partition-by": "base_timestamp"} }' \
    -H "Content-Type: application/json" -H "Authorization: Bearer 962a235f2661439d923bdf3def535e0f7acb6890fb241822a1cd9cd47b636db5"

Got response:

OK

We will use push_token to send new data.

curl "https://app.manyevents.cloud/push-api/v0-unstable/push-event" -d '{"x-manyevents-name": "main",
    "span_id": "xxxx",
    "span_start_time": 1234567890,
    "span_end_time": 1234567892,
    "base_timestamp": 1234567892,
    "base_parent_span_id": "xxxx",
    "base_message": "test message"}' \
    -H "Content-Type: application/json" -H "Authorization: Bearer 736b9beb1cfe82f53dba1204df9f4f89efb7f56c8c95a54677e6edcbaca9b034"

Response:

{"is_success":true,"message_code":null}

The data is in Clickhouse now.

Run for the development

cp .env.example .env
# edit secrets

Export all variables from .env to global environment. We could use dotenv, but we have errors variables weren't passing to children threads.

set -a; source .env; set +a

Setup infra:

docker compose up -d --build

Then run data migrations in PostgreSQL:

make migrate

Then:

# Just run it
make run

# Run tests once
make test

# Run tests permanently watching for the source changes
make testw

# Run building binary rerunning on code changes
make runw

Pre-commit

For regular development pre-commit installation is recommended. Path to cargo must be added in PATH variable in pre-commit. This is currently handled in fmt-pre-commit and test-pre-commit in Makefile.

# For Mac
brew install pre-commit
pre-commit install

# Through uv
uv tool install pre-commit
uv tool run pre-commit install

I use Miro board for brainstorming. There various things could be found for the product development.

Install tools

$ cargo install cargo-watch --locked
$ cargo install sqlx-cli

$ sqlx migrate add --source manyevents/db/migrations create_tables