datus-statsig-plugin
A Datus plugin that wraps the Statsig Console API
(version 20240601) as datus statsig. It focuses on the data-analysis surface
of the API: reading metrics and experiment results, authoring warehouse-native
metric SQL, and driving ETL ingestion — not feature-flag / project management.
Install
pip install -e datus-statsig-plugin
datus statsig --help
Configure
Add a profile under agent.plugins.statsig in your agent.yml:
agent:
plugins:
statsig:
prod:
default: true
api_key: ${STATSIG_CONSOLE_API_KEY} # secret — env var reference, never a literal
# optional:
api_base_url: https://statsigapi.net # Console API root (plugin appends /console/v1)
api_version: "20240601"
timeout: 30
Create a Console API key at console.statsig.com/api_keys. Or run the
bundled statsig-setup skill for a guided setup.
| Field | Required | Secret | Default |
|---|---|---|---|
api_key |
yes | yes (${VAR}) |
— |
api_base_url |
no | no | https://statsigapi.net |
api_version |
no | no | 20240601 |
timeout |
no | no | 30 |
Commands
datus statsig [--profile <env>] <group> <subcommand> [args...]
| Group | Subcommands | Posture |
|---|---|---|
metrics |
list, get, sql, values / create, update, reload | reads allow · writes ask |
metric-source |
list, get / create, update, delete | reads allow · writes ask |
experiments |
list, get, pulse, summary, exposures, pulse-status / load-pulse | reads allow · writes ask |
ingestion |
get, runs, run, status, schedule-get / backfill, schedule-set | reads allow · writes ask |
warehouse-connections |
update | ask |
events |
list, get | allow |
logs |
query | allow |
reports |
get | allow |
describe |
<group> <subcommand> |
allow (prints a write command's body template) |
Output is JSON by default (--compact for one line; -o table|plain|yaml).
Write commands take their body via --json '<inline>' or --json-file <path>
(warehouse-connections update accepts only --json-file, since it carries
credentials). Run datus statsig describe <group> <subcommand> — or add
--help — to see the body template; --dry-run validates without persisting.
Rate limits: mutations are capped at ~100/10s and ~900/15min per project.
Permissions
When the agent runs these commands through its bash tool, read-only commands
(and describe) auto-run; every mutation confirms under both the normal and
auto permission profiles (re-running a write costs warehouse compute and
consumes the mutation rate limit).
Bundled skills
statsig— how to use the CLI for metric/experiment analysis and SQL authoring.statsig-setup— configure an environment profile.
Development
pip install -e 'datus-statsig-plugin[dev]'
pytest datus-statsig-plugin
The plugin never imports datus — Datus is the config broker and calls the
plugin by duck typing.
Metadata
Release files for datus-statsig-plugin 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| datus_statsig_plugin-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for datus_statsig_plugin-0.1.0-py3-none-any.whl |
Release files / datus_statsig_plugin-0.1.0-py3-none-any.whl
| Download URL | datus_statsig_plugin-0.1.0-py3-none-any.whl |
|---|---|
| Size | 28.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
02eaaffba01bdadc8e75300a462931576aa3567d92f55cea566904f89f23a96c
|
|
BLAKE2b-256 checksum How to use checksums |
1df56212c205955e9eb1d76dad90070aa52c49f3b79175152bf3ed7cde57ebec
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.10
|
Security for datus-statsig-plugin 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.