refactor(iota-graphql-rpc): change log level for Subscription responses #9294
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The latest updates on your projects. Learn more about Vercel for GitHub. 6 Skipped Deployments
|
iota-ci
added
infrastructure
kodemartin
reviewed
Nov 17, 2025
tomxey
approved these changes
Nov 17, 2025
sergiupopescu199
merged commit 8d7cc6f
into
sc-platform/feat/streaming-support
37 of 39 checks passed
sergiupopescu199
deleted the
sc-platform/issue-9114-graphql-log-polution-subscriptions
branch
sergiupopescu199
added a commit
that referenced
this pull request
Nov 20, 2025
…es (#9294) # Description of change This PR modifies the log level from `INFO` to `DEBUG` for Subscription Responses in the Logger extension to avoid log pollution. Since every item received from the Subscription stream is treated as a GraphQL Response. With multiple subscribers at the same time, the logs become too polluted and hard to read. ## Links to any relevant issues fixes #9114 ## How the change has been tested - [x] Basic tests (linting, compilation, formatting, unit/integration tests) - [ ] Patch-specific tests (correctness, functionality coverage) - Ran the GraphQL server by using the iota cli ```shell RUST_LOG=off,iota_graphql_rpc=info cargo r --features indexer -- start --force-regenesis --with-indexer --with-graphql ``` When making Subscription requests, the logs were no longer present. If enabling `RUST_LOG=off,iota_graphql_rpc=debug`, the logs were visible. ```shell 2025-11-14T14:58:14.201495Z INFO iota_graphql_rpc::extensions::logger: [Validation] query_id=9eef57e6-edf0-42cd-829b-6e4b469b8919 session_id=127.0.0.1:52594 complexity=3 depth=2 2025-11-14T14:58:14.456023Z DEBUG iota_graphql_rpc::extensions::logger: [Subscription] {transactions: {__typename: "TransactionBlock", digest: "4aQ17xRBjo9bCgQLcKUdqatUjm7Yck2kUtbJTfwDfj4c"}} query_id=9eef57e6-edf0-42cd-829b-6e4b469b8919 session_id=127.0.0.1:52594 ``` ### Infrastructure QA (only required for crates that are maintained by @iotaledger/infrastructure) - [ ] Synchronization of the indexer from genesis for a network including migration objects. - [ ] Restart of indexer synchronization locally without resetting the database. - [ ] Restart of indexer synchronization on a production-like database. - [ ] Deployment of services using Docker. - [ ] Verification of API backward compatibility. > [!NOTE] > This patch does not affect the normal operations of the indexer; thus, no tests were conducted.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description of change
This PR modifies the log level from
INFOtoDEBUGfor Subscription Responses in the Logger extension to avoid log pollution.Since every item received from the Subscription stream is treated as a GraphQL Response. With multiple subscribers at the same time, the logs become too polluted and hard to read.
Links to any relevant issues
fixes #9114
How the change has been tested
Basic tests (linting, compilation, formatting, unit/integration tests)
Patch-specific tests (correctness, functionality coverage)
Ran the GraphQL server by using the iota cli
When making Subscription requests, the logs were no longer present. If enabling
RUST_LOG=off,iota_graphql_rpc=debug, the logs were visible.2025-11-14T14:58:14.201495Z INFO iota_graphql_rpc::extensions::logger: [Validation] query_id=9eef57e6-edf0-42cd-829b-6e4b469b8919 session_id=127.0.0.1:52594 complexity=3 depth=2 2025-11-14T14:58:14.456023Z DEBUG iota_graphql_rpc::extensions::logger: [Subscription] {transactions: {__typename: "TransactionBlock", digest: "4aQ17xRBjo9bCgQLcKUdqatUjm7Yck2kUtbJTfwDfj4c"}} query_id=9eef57e6-edf0-42cd-829b-6e4b469b8919 session_id=127.0.0.1:52594Infrastructure QA (only required for crates that are maintained by @iotaledger/infrastructure)
Note
This patch does not affect the normal operations of the indexer; thus, no tests were conducted.