summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJerop Kipruto <[email protected]>2025-06-15 21:28:29 -0400
committerGitHub <[email protected]>2025-06-15 21:28:29 -0400
commit7f06ad40c562c22fa173855e934b8141b67fd92c (patch)
tree53bad3e4bf2b1c23beab9223b63ed7613e612b99
parente772dc2b854dff3e9949ce4a16918e97d656d6a2 (diff)
Add a command for starting Gemini CLI with GCP telemetry (#1079)
This command enables starting the application with GCP telemetry: ```shell npm run start:gcp ```
-rw-r--r--docs/core/telemetry.md2
-rw-r--r--package.json3
2 files changed, 4 insertions, 1 deletions
diff --git a/docs/core/telemetry.md b/docs/core/telemetry.md
index 9dc222f5..cb9ea2b7 100644
--- a/docs/core/telemetry.md
+++ b/docs/core/telemetry.md
@@ -23,6 +23,8 @@ This entire system is built on the **[OpenTelemetry] (OTEL)** standard, allowing
1. **View Data:** The script will provide links to view your telemetry data (traces, metrics, logs) in the Google Cloud Console.
1. **Details:** Refer to documentation for telemetry in [Google Cloud](#google-cloud).
+> **Note:** You can also use `npm run start:gcp` as a shorthand for running the CLI with GCP telemetry.
+
### Local Telemetry with Jaeger UI (for Traces)
1. **Run the Command:** Execute the following command from the project root:
diff --git a/package.json b/package.json
index 563e09ac..bbf3bb00 100644
--- a/package.json
+++ b/package.json
@@ -35,7 +35,8 @@
"publish:sandbox": "node scripts/publish-sandbox.js",
"publish:npm": "npm publish --workspaces ${NPM_PUBLISH_TAG:+--tag=$NPM_PUBLISH_TAG} ${NPM_DRY_RUN:+--dry-run}",
"publish:release": "npm run build:packages && npm run prepare:cli-packagejson && npm run build:docker && npm run tag:docker && npm run publish:sandbox && npm run publish:npm",
- "telemetry": "node scripts/telemetry.js"
+ "telemetry": "node scripts/telemetry.js",
+ "start:gcp": "npm run telemetry -- --target=gcp & npm start"
},
"bin": {
"gemini": "bundle/gemini.js"