| name | grammarly-observability |
| description | Implement Grammarly observability with metrics and logging.
Use when setting up monitoring, tracking API performance,
or implementing alerting for Grammarly integrations.
Trigger with phrases like "grammarly monitoring", "grammarly metrics",
"grammarly observability", "grammarly logging", "grammarly alerts".
|
| allowed-tools | Read, Write, Edit |
| version | 1.8.0 |
| license | MIT |
| author | Jeremy Longshore <jeremy@intentsolutions.io> |
| tags | ["saas","grammarly","writing"] |
| compatibility | Designed for Claude Code |
Grammarly Observability
Overview
Grammarly API integrations process user text through scoring, AI rewriting, and plagiarism endpoints where latency and accuracy directly affect user experience. Monitor text check response times, suggestion quality signals, API error rates, and token consumption to stay within rate limits. Catching degradation early prevents users from seeing stale suggestions or silent failures in real-time editing flows.
Key Metrics
| Metric | Type | Target | Alert Threshold |
|---|
| Text check latency p95 | Histogram | < 300ms | > 800ms |
| API error rate | Gauge | < 1% | > 5% |
| Suggestion acceptance rate | Gauge | > 40% | < 20% (quality signal) |
| Token usage (daily) | Counter | < 80% quota | > 90% quota |
| Plagiarism check latency | Histogram | < 2s | > 5s |
| AI rewrite throughput | Counter | Stable | Drop > 30% |
Instrumentation
async function trackGrammarlyCall(api: 'score' | 'ai' | 'plagiarism', textLen: number, fn: () => Promise<any>) {
const start = Date.now();
try {
const result = await fn();
metrics.histogram('grammarly.api.latency', Date.now() - start, { api });
metrics.increment(, { api });
metrics.(, textLen, { api });
result;
} (err) {
metrics.(, { api, : err. });
err;
}
}
