Chisle
코딩 에이전트 플러그인, 20개 실시간 작업에서 기본 모델 52% 활용, 간결한 페르소나와 출력 압축 제공
아직 감지된 업데이트가 없습니다. GitHub 릴리스가 나오면 여기에 보입니다.
Compare TCO for all metric providers including self hosted
README 전체를 불러오는 중입니다.
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