From 8993b6c54194763a71d2a5adf1c704a7070eebfa Mon Sep 17 00:00:00 2001 From: Matthew McNeely Date: Mon, 21 Sep 2026 14:51:25 -0400 Subject: [PATCH] docs: remove expose_trace references The `expose_trace` flag is being removed from Dgraph in dgraph-io/dgraph#9593. Drop it from the lambda-server Docker example and correct the metrics section of the debug-information page, which described the flag as gating `/debug/vars`. It never did. Co-Authored-By: Claude Opus 5 (1M context) --- .../docs-learn/howto/retrieving-debug-information.md | 2 +- docusaurus-docs/docs/installation/lambda-server.md | 2 +- .../version-v24.1/installation/lambda-server.md | 2 +- .../version-v25.1/installation/lambda-server.md | 2 +- .../version-v25.2/installation/lambda-server.md | 2 +- .../version-v25.3/installation/lambda-server.md | 2 +- .../version-v25.4/installation/lambda-server.md | 2 +- 7 files changed, 7 insertions(+), 7 deletions(-) diff --git a/docusaurus-docs/docs-learn/howto/retrieving-debug-information.md b/docusaurus-docs/docs-learn/howto/retrieving-debug-information.md index 8781dee3..a8fdb535 100644 --- a/docusaurus-docs/docs-learn/howto/retrieving-debug-information.md +++ b/docusaurus-docs/docs-learn/howto/retrieving-debug-information.md @@ -6,7 +6,7 @@ Each Dgraph data node exposes profile over `/debug/pprof` endpoint and metrics o ## Metrics Information -If you are collecting these metrics from outside the Dgraph instance you need to pass `--expose_trace=true` flag, otherwise there metrics can be collected by connecting to the instance over localhost. +The `/debug/vars` endpoint is served on the Alpha or Zero HTTP port and is not restricted by source IP, so any client that can reach that port can read these metrics. No flag is required to collect them remotely. If you don't want them publicly readable, restrict access to the HTTP port at the network layer. ``` curl http://:/debug/vars diff --git a/docusaurus-docs/docs/installation/lambda-server.md b/docusaurus-docs/docs/installation/lambda-server.md index 6bfdef84..d7fc4369 100644 --- a/docusaurus-docs/docs/installation/lambda-server.md +++ b/docusaurus-docs/docs/installation/lambda-server.md @@ -51,7 +51,7 @@ curl localhost:8686/graphql-worker -H "Content-Type: application/json" -d '{"res If you're using Docker, you need to add the `--graphql` superflag's `lambda-url` option to your Alpha configuration. For example: ```yml - command: /gobin/dgraph alpha --zero=zero1:5180 -o 100 --expose_trace --trace ratio=1.0 + command: /gobin/dgraph alpha --zero=zero1:5180 -o 100 --trace ratio=1.0 --profile_mode block --block_rate 10 --logtostderr -v=2 --security whitelist=10.0.0.0/8,172.16.0.0/12,192.168.0.0/16 --my=alpha1:7180 --graphql lambda-url=http://lambda:8686/graphql-worker diff --git a/docusaurus-docs/docs_versioned_docs/version-v24.1/installation/lambda-server.md b/docusaurus-docs/docs_versioned_docs/version-v24.1/installation/lambda-server.md index 6bfdef84..d7fc4369 100644 --- a/docusaurus-docs/docs_versioned_docs/version-v24.1/installation/lambda-server.md +++ b/docusaurus-docs/docs_versioned_docs/version-v24.1/installation/lambda-server.md @@ -51,7 +51,7 @@ curl localhost:8686/graphql-worker -H "Content-Type: application/json" -d '{"res If you're using Docker, you need to add the `--graphql` superflag's `lambda-url` option to your Alpha configuration. For example: ```yml - command: /gobin/dgraph alpha --zero=zero1:5180 -o 100 --expose_trace --trace ratio=1.0 + command: /gobin/dgraph alpha --zero=zero1:5180 -o 100 --trace ratio=1.0 --profile_mode block --block_rate 10 --logtostderr -v=2 --security whitelist=10.0.0.0/8,172.16.0.0/12,192.168.0.0/16 --my=alpha1:7180 --graphql lambda-url=http://lambda:8686/graphql-worker diff --git a/docusaurus-docs/docs_versioned_docs/version-v25.1/installation/lambda-server.md b/docusaurus-docs/docs_versioned_docs/version-v25.1/installation/lambda-server.md index 6bfdef84..d7fc4369 100644 --- a/docusaurus-docs/docs_versioned_docs/version-v25.1/installation/lambda-server.md +++ b/docusaurus-docs/docs_versioned_docs/version-v25.1/installation/lambda-server.md @@ -51,7 +51,7 @@ curl localhost:8686/graphql-worker -H "Content-Type: application/json" -d '{"res If you're using Docker, you need to add the `--graphql` superflag's `lambda-url` option to your Alpha configuration. For example: ```yml - command: /gobin/dgraph alpha --zero=zero1:5180 -o 100 --expose_trace --trace ratio=1.0 + command: /gobin/dgraph alpha --zero=zero1:5180 -o 100 --trace ratio=1.0 --profile_mode block --block_rate 10 --logtostderr -v=2 --security whitelist=10.0.0.0/8,172.16.0.0/12,192.168.0.0/16 --my=alpha1:7180 --graphql lambda-url=http://lambda:8686/graphql-worker diff --git a/docusaurus-docs/docs_versioned_docs/version-v25.2/installation/lambda-server.md b/docusaurus-docs/docs_versioned_docs/version-v25.2/installation/lambda-server.md index 6bfdef84..d7fc4369 100644 --- a/docusaurus-docs/docs_versioned_docs/version-v25.2/installation/lambda-server.md +++ b/docusaurus-docs/docs_versioned_docs/version-v25.2/installation/lambda-server.md @@ -51,7 +51,7 @@ curl localhost:8686/graphql-worker -H "Content-Type: application/json" -d '{"res If you're using Docker, you need to add the `--graphql` superflag's `lambda-url` option to your Alpha configuration. For example: ```yml - command: /gobin/dgraph alpha --zero=zero1:5180 -o 100 --expose_trace --trace ratio=1.0 + command: /gobin/dgraph alpha --zero=zero1:5180 -o 100 --trace ratio=1.0 --profile_mode block --block_rate 10 --logtostderr -v=2 --security whitelist=10.0.0.0/8,172.16.0.0/12,192.168.0.0/16 --my=alpha1:7180 --graphql lambda-url=http://lambda:8686/graphql-worker diff --git a/docusaurus-docs/docs_versioned_docs/version-v25.3/installation/lambda-server.md b/docusaurus-docs/docs_versioned_docs/version-v25.3/installation/lambda-server.md index 6bfdef84..d7fc4369 100644 --- a/docusaurus-docs/docs_versioned_docs/version-v25.3/installation/lambda-server.md +++ b/docusaurus-docs/docs_versioned_docs/version-v25.3/installation/lambda-server.md @@ -51,7 +51,7 @@ curl localhost:8686/graphql-worker -H "Content-Type: application/json" -d '{"res If you're using Docker, you need to add the `--graphql` superflag's `lambda-url` option to your Alpha configuration. For example: ```yml - command: /gobin/dgraph alpha --zero=zero1:5180 -o 100 --expose_trace --trace ratio=1.0 + command: /gobin/dgraph alpha --zero=zero1:5180 -o 100 --trace ratio=1.0 --profile_mode block --block_rate 10 --logtostderr -v=2 --security whitelist=10.0.0.0/8,172.16.0.0/12,192.168.0.0/16 --my=alpha1:7180 --graphql lambda-url=http://lambda:8686/graphql-worker diff --git a/docusaurus-docs/docs_versioned_docs/version-v25.4/installation/lambda-server.md b/docusaurus-docs/docs_versioned_docs/version-v25.4/installation/lambda-server.md index 6bfdef84..d7fc4369 100644 --- a/docusaurus-docs/docs_versioned_docs/version-v25.4/installation/lambda-server.md +++ b/docusaurus-docs/docs_versioned_docs/version-v25.4/installation/lambda-server.md @@ -51,7 +51,7 @@ curl localhost:8686/graphql-worker -H "Content-Type: application/json" -d '{"res If you're using Docker, you need to add the `--graphql` superflag's `lambda-url` option to your Alpha configuration. For example: ```yml - command: /gobin/dgraph alpha --zero=zero1:5180 -o 100 --expose_trace --trace ratio=1.0 + command: /gobin/dgraph alpha --zero=zero1:5180 -o 100 --trace ratio=1.0 --profile_mode block --block_rate 10 --logtostderr -v=2 --security whitelist=10.0.0.0/8,172.16.0.0/12,192.168.0.0/16 --my=alpha1:7180 --graphql lambda-url=http://lambda:8686/graphql-worker