blockmine 1.24.0 → 1.27.0

package/.claude/skills/observability-engineering/resources/logs-aggregation.md

@@ -1,118 +0,0 @@
-# Logs Aggregation
-
-Guide to ELK Stack, Loki, and structured logging for centralized log management.
-
-## ELK Stack (Elasticsearch, Logstash, Kibana)
-
-```yaml
-# docker-compose.yml
-version: '3'
-services:
-  elasticsearch:
-    image: elasticsearch:8.11.0
-    environment:
-      - discovery.type=single-node
-    ports:
-      - "9200:9200"
-
-  logstash:
-    image: logstash:8.11.0
-    volumes:
-      - ./logstash.conf:/usr/share/logstash/pipeline/logstash.conf
-
-  kibana:
-    image: kibana:8.11.0
-    ports:
-      - "5601:5601"
-```
-
-## Structured Logging
-
-```typescript
-import winston from 'winston';
-
-const logger = winston.createLogger({
-  format: winston.format.json(),
-  transports: [
-    new winston.transports.Console(),
-  ],
-});
-
-logger.info('User logged in', {
-  userId: 'user-123',
-  ipAddress: req.ip,
-  traceId: span.spanContext().traceId,  // Correlation
-  timestamp: new Date().toISOString(),
-});
-
-// Output:
-// {"level":"info","message":"User logged in","userId":"user-123","traceId":"abc123",...}
-```
-
-## Grafana Loki
-
-```yaml
-# loki-config.yaml
-auth_enabled: false
-
-server:
-  http_listen_port: 3100
-
-ingester:
-  lifecycler:
-    ring:
-      kvstore:
-        store: inmemory
-      replication_factor: 1
-
-schema_config:
-  configs:
-    - from: 2020-10-24
-      store: boltdb-shipper
-      object_store: s3
-      schema: v11
-```
-
-```typescript
-// Ship logs to Loki
-import Pino from 'pino';
-
-const logger = Pino({
-  transport: {
-    target: 'pino-loki',
-    options: {
-      batching: true,
-      interval: 5,
-      host: 'http://loki:3100',
-      labels: {
-        service: 'my-app',
-        env: 'production',
-      },
-    },
-  },
-});
-```
-
-## Log Levels
-
-```typescript
-logger.error('Payment failed', { orderId: '123', error: err.message });
-logger.warn('High memory usage', { memoryMB: 850 });
-logger.info('User registered', { userId: 'user-456' });
-logger.debug('Cache miss', { key: 'user:123' });
-```
-
-## Best Practices
-
-✅ Use structured logging (JSON)
-✅ Include trace IDs for correlation
-✅ Log at appropriate levels
-✅ Avoid logging sensitive data (PII, passwords)
-✅ Set retention policies (30-90 days)
-✅ Index important fields
-
----
-
-**Related Resources:**
-- correlation-strategies.md - Linking logs with traces
-- observability-cost-optimization.md - Log retention costs

package/.claude/skills/observability-engineering/resources/observability-cost-optimization.md

@@ -1,141 +0,0 @@
-# Observability Cost Optimization
-
-Guide to managing observability costs through sampling, retention policies, and efficient practices.
-
-## Sampling Strategies
-
-### Head-Based Sampling
-```typescript
-// Sample 10% of traces
-const sampler = new TraceIdRatioBasedSampler(0.1);
-
-const sdk = new NodeSDK({
-  sampler,
-  // ...
-});
-
-// Pros: Simple, predictable cost
-// Cons: May miss rare errors
-```
-
-### Tail-Based Sampling
-```typescript
-// Sample based on outcome (keep all errors, 1% of success)
-const tailSampler = {
-  shouldSample: (span) => {
-    if (span.status.code === SpanStatusCode.ERROR) {
-      return true;  // Keep all errors
-    }
-    if (span.attributes['http.status_code'] >= 500) {
-      return true;  // Keep server errors
-    }
-    return Math.random() < 0.01;  // 1% of successful requests
-  },
-};
-
-// Pros: Keeps important traces, lower cost
-// Cons: More complex
-```
-
-## Retention Policies
-
-```
-Hot storage (recent, fast):
-- Traces: 7 days
-- Logs: 14 days
-- Metrics: 30 days
-
-Warm storage (archived, slower):
-- Traces: 30 days
-- Logs: 90 days
-- Metrics: 1 year
-
-Cold storage (compliance):
-- Logs: 7 years (compressed)
-```
-
-## Cost Breakdown
-
-```
-Typical observability costs (10 services, 1M RPM):
-
-DataDog:
-- APM: $2,000/month (100M spans)
-- Logs: $1,500/month (500 GB)
-- Metrics: $500/month
-- Total: $4,000/month
-
-Self-Hosted (Jaeger + Loki + Prometheus):
-- Infrastructure: $800/month
-- Maintenance: $3,000/month (0.3 engineer)
-- Total: $3,800/month
-
-Savings with optimization:
-- 90% sampling: $400 APM (vs $2,000)
-- 30-day retention: $500 logs (vs $1,500)
-- Total: $1,400/month (65% reduction)
-```
-
-## Optimization Strategies
-
-### 1. Sample Aggressively
-```
-High-volume endpoints: 1% sample rate
-Low-volume endpoints: 100% sample rate
-Errors: Always keep
-```
-
-### 2. Reduce Log Volume
-```typescript
-// Don't log every request
-if (req.path !== '/health' && req.path !== '/metrics') {
-  logger.info('Request', { method: req.method, path: req.path });
-}
-
-// Sample logs
-if (Math.random() < 0.1) {  // 10% of logs
-  logger.debug('Debug info', { ...details });
-}
-```
-
-### 3. Optimize Metric Cardinality
-```typescript
-// ❌ Bad: Unbounded cardinality
-requestCounter.add(1, { userId: req.userId });  // Millions of users
-
-// ✅ Good: Bounded cardinality
-requestCounter.add(1, { endpoint: req.route });  // ~100 endpoints
-```
-
-### 4. Use Cheaper Storage
-```
-S3 Glacier for old logs: $0.004/GB (vs $0.023/GB Standard)
-83% cheaper for infrequently accessed data
-```
-
-## Monitoring Observability Costs
-
-```typescript
-// Track observability data volume
-observabilityCostGauge.set(dailySpanCount * 0.0001);  // $0.0001 per span
-
-// Alert on cost spikes
-if (dailyObservabilityCost > threshold) {
-  alert('Observability costs exceeded budget');
-}
-```
-
-## Best Practices
-
-✅ Sample high-volume endpoints
-✅ Always keep errors
-✅ Set aggressive retention policies
-✅ Reduce metric cardinality
-✅ Use cheaper storage tiers
-✅ Monitor observability costs
-
----
-
-**Related Resources:**
-- distributed-tracing.md - Sampling implementation
-- logs-aggregation.md - Log retention

package/.claude/skills/observability-engineering/resources/opentelemetry.md

@@ -1,110 +0,0 @@
-# OpenTelemetry
-
-Comprehensive guide to OpenTelemetry (OTEL) for vendor-neutral observability instrumentation.
-
-## Setup
-
-```typescript
-import { NodeSDK } from '@opentelemetry/sdk-node';
-import { getNodeAutoInstrumentations } from '@opentelemetry/auto-instrumentations-node';
-import { JaegerExporter } from '@opentelemetry/exporter-jaeger';
-
-const sdk = new NodeSDK({
-  traceExporter: new JaegerExporter({
-    endpoint: 'http://jaeger:14268/api/traces',
-  }),
-  instrumentations: [getNodeAutoInstrumentations()],
-});
-
-sdk.start();
-```
-
-## Auto-Instrumentation
-
-```typescript
-// Auto-instruments: HTTP, Express, Prisma, Redis, etc.
-import { getNodeAutoInstrumentations } from '@opentelemetry/auto-instrumentations-node';
-
-const instrumentations = getNodeAutoInstrumentations({
-  '@opentelemetry/instrumentation-http': {
-    ignoreIncomingPaths: ['/health'],
-  },
-  '@opentelemetry/instrumentation-express': {
-    enabled: true,
-  },
-  '@opentelemetry/instrumentation-prisma': {
-    enabled: true,
-  },
-});
-```
-
-## Manual Instrumentation
-
-```typescript
-import { trace, SpanKind } from '@opentelemetry/api';
-
-const tracer = trace.getTracer('my-app', '1.0.0');
-
-async function processOrder(order) {
-  const span = tracer.startSpan('processOrder', {
-    kind: SpanKind.INTERNAL,
-    attributes: {
-      'order.id': order.id,
-      'order.total': order.total,
-    },
-  });
-
-  try {
-    await validateOrder(order);
-    await chargePayment(order);
-    await shipOrder(order);
-
-    span.setAttribute('order.status', 'completed');
-  } catch (error) {
-    span.recordException(error);
-    span.setStatus({ code: SpanStatusCode.ERROR });
-    throw error;
-  } finally {
-    span.end();
-  }
-}
-```
-
-## OTEL Collector
-
-```yaml
-# otel-collector-config.yaml
-receivers:
-  otlp:
-    protocols:
-      grpc:
-      http:
-
-processors:
-  batch:
-  memory_limiter:
-    limit_mib: 1024
-
-exporters:
-  jaeger:
-    endpoint: jaeger:14250
-  prometheus:
-    endpoint: "0.0.0.0:8889"
-
-service:
-  pipelines:
-    traces:
-      receivers: [otlp]
-      processors: [batch]
-      exporters: [jaeger]
-    metrics:
-      receivers: [otlp]
-      processors: [batch]
-      exporters: [prometheus]
-```
-
----
-
-**Related Resources:**
-- distributed-tracing.md - Tracing concepts
-- apm-tools.md - APM integration