Chisle
The coding-agent plugin that bills 52% of a bare model across 20 live tasks. Terse persona + tool-output compressor + context diet.
Compare costs across different observability platforms
Translation pending
Developer toolsTypeScript · JavaScriptGitHub @poulsbopeteOnlineOwner unconfirmed
Have you tried it? One tap is enough. No sign-in needed.
No updates detected yet. GitHub releases will appear here.
Compare TCO for all metric providers including self hosted
Translation pending
Loading the full README.
Read the full README ↗A Next.js application that helps you compare the costs of different observability platforms based on metric volume and tag cardinality.
npm install
Required for OpenTelemetry:
Create a .env.local file in the root directory with the following variables:
# OpenTelemetry Configuration (REQUIRED)
OTEL_EXPORTER_OTLP_ENDPOINT=https://your-deployment-id.ingest.region.aws.elastic.cloud:443
OTEL_API_KEY=your-elastic-api-key-here
# Optional OpenTelemetry Configuration
OTEL_SERVICE_NAME=metrics-compare
OTEL_SERVICE_VERSION=0.1.0
OTEL_DEPLOYMENT_ENVIRONMENT=production
Note: OTEL_EXPORTER_OTLP_ENDPOINT and OTEL_API_KEY are required. OpenTelemetry will not initialize without them. Get these values from your Elastic Cloud dashboard.
npm run dev
Open http://localhost:3000 in your browser.
npm run build
npm start
VERCEL_ENV_SETUP.md for detailed instructionsOTEL_API_KEY (mark as sensitive)OTEL_EXPORTER_OTLP_ENDPOINT, OTEL_SERVICE_NAME, OTEL_SERVICE_VERSION, OTEL_DEPLOYMENT_ENVIRONMENTVERCEL_ENV if OTEL_DEPLOYMENT_ENVIRONMENT is not setOr use the Vercel CLI:
npm i -g vercel
vercel
The tool calculates metric volume by:
This demonstrates how adding tags with high cardinality can dramatically increase metric volume and costs.
The app includes OpenTelemetry instrumentation that automatically sends traces and metrics to Elastic Observability. The instrumentation:
To configure OpenTelemetry, set the environment variables in .env.local or in your Vercel project settings.
MIT