@jaypie/mcp 0.7.21 → 0.7.22
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
|
@@ -9,7 +9,7 @@ import { gt } from 'semver';
|
|
|
9
9
|
/**
|
|
10
10
|
* Docs Suite - Documentation services (skill, version, release_notes)
|
|
11
11
|
*/
|
|
12
|
-
const BUILD_VERSION_STRING = "@jaypie/mcp@0.7.
|
|
12
|
+
const BUILD_VERSION_STRING = "@jaypie/mcp@0.7.22#e20270cd"
|
|
13
13
|
;
|
|
14
14
|
const __filename$1 = fileURLToPath(import.meta.url);
|
|
15
15
|
const __dirname$1 = path.dirname(__filename$1);
|
package/package.json
CHANGED
|
@@ -0,0 +1,15 @@
|
|
|
1
|
+
---
|
|
2
|
+
version: 1.2.2
|
|
3
|
+
date: 2026-02-18
|
|
4
|
+
summary: Add opt-in Datadog log forwarding transport for non-Lambda environments
|
|
5
|
+
---
|
|
6
|
+
|
|
7
|
+
## Changes
|
|
8
|
+
|
|
9
|
+
- Add `DatadogLogTransport` that ships logs directly to Datadog's Logs API via HTTPS when enabled by env vars
|
|
10
|
+
- Transport activates when `DATADOG_LOCAL_FORWARDING=true` and `DATADOG_API_KEY` is set — zero application code changes needed
|
|
11
|
+
- Batches logs (flush every 5s or at 100 entries) with atomic buffer swap and best-effort flush on process exit
|
|
12
|
+
- Auto-tags entries with `ddsource`, `service`, `env`, and `hostname` from DD_* and PROJECT_* env vars
|
|
13
|
+
- Transport errors are silently swallowed and never affect stdout logging
|
|
14
|
+
- Export `isDatadogForwardingEnabled()` and `_resetDatadogTransport()` for inspection and Lambda lifecycle
|
|
15
|
+
- `init()` now resets the Datadog transport so env vars are re-read between Lambda invocations
|
package/skills/datadog.md
CHANGED
|
@@ -50,6 +50,37 @@ log.error("Payment failed", {
|
|
|
50
50
|
});
|
|
51
51
|
```
|
|
52
52
|
|
|
53
|
+
## Direct Log Forwarding (Non-Lambda)
|
|
54
|
+
|
|
55
|
+
For local dev, eval runs, and CI where CloudWatch subscription filters aren't available, enable direct HTTP forwarding to Datadog's Logs API:
|
|
56
|
+
|
|
57
|
+
```bash
|
|
58
|
+
DATADOG_LOCAL_FORWARDING=true DATADOG_API_KEY=your-key npm run dev
|
|
59
|
+
```
|
|
60
|
+
|
|
61
|
+
This activates automatically in `@jaypie/logger` — zero code changes needed. Logs are batched (flush every 5s or 100 entries) and shipped via HTTPS to `http-intake.logs.{DD_SITE}/api/v2/logs`.
|
|
62
|
+
|
|
63
|
+
### Environment Variables
|
|
64
|
+
|
|
65
|
+
| Variable | Description | Default |
|
|
66
|
+
|----------|-------------|---------|
|
|
67
|
+
| `DATADOG_LOCAL_FORWARDING` | Enable forwarding (`true`/`false`) | `false` |
|
|
68
|
+
| `DATADOG_API_KEY` | Datadog API key (required) | — |
|
|
69
|
+
| `DD_SITE` | Datadog intake site | `datadoghq.com` |
|
|
70
|
+
| `DD_SERVICE` / `PROJECT_SERVICE` | Service tag | `unknown` |
|
|
71
|
+
| `DD_ENV` / `PROJECT_ENV` | Environment tag | `local` |
|
|
72
|
+
| `DD_HOST` / `PROJECT_HOST` | Hostname tag | `os.hostname()` |
|
|
73
|
+
|
|
74
|
+
### Inspection
|
|
75
|
+
|
|
76
|
+
```typescript
|
|
77
|
+
import { isDatadogForwardingEnabled } from "@jaypie/logger";
|
|
78
|
+
|
|
79
|
+
if (isDatadogForwardingEnabled()) {
|
|
80
|
+
// Transport is active
|
|
81
|
+
}
|
|
82
|
+
```
|
|
83
|
+
|
|
53
84
|
## @jaypie/datadog Package
|
|
54
85
|
|
|
55
86
|
The `@jaypie/datadog` package provides utilities:
|