Pages are files.
MDX routes and named SQL live in a git repo. Add a report by adding a file.
SlopKit Analytics
One solution for
all analytics
Track events from a website, commands from a CLI, or product performance metrics, all in one store. Join the data from those sources and write your own reports. All in one tool.
-
Collector
HTTP ingest for events and metrics. Nothing else writes the store. Run it next to the product binary if you want.
-
Store
One file. Events and metrics land in it. A report can use both.
-
Panel
A second process. It reads that store, runs named SQL, and serves MDX from git.
Events and metrics share a file.
track rows and metric points sit in one store, so a report can use both.
The collector can ship in the product.
A binary can run it on the laptop, write locally, and show stats without an uplink.
You run the hosted collector
You are not renting a popular cloud analytics stack. You pick the host, what to collect, and when.
-
Sovereignty
Nobody else can drop a feature or lock the account. The process and the file stay with you.
-
Full control
No stock events and no stock charts. You name the tracks and metrics. You write the pages.
-
One collector, many products
One app. The write key stamps each row. Two products on the same collector do not see each other's dashboards or data.
-
Code-first
A report is an MDX file. The agent commits it with the feature.
Offline does not drop events
The product's collector keeps writing when the laptop is offline. When the network is back, it relays to your hosted collector.
Product collector Local store Your hosted collector
Agents write the pages
Two skills. Install them and stay on the feature.
analytics-page
Write a page from names already in the catalog. Do not invent events.
analytics-instrument
Add a new event or metric in the product. Then use analytics-page for its report.