8000 DOC-391 | Release notes for AQL graph traversal tracing (#1323) · larsborn/arangodb-docs@192c921 · GitHub
[go: up one dir, main page]

Skip to content

Commit 192c921

Browse files
Simran-Bnerpaula
andauthored
DOC-391 | Release notes for AQL graph traversal tracing (arangodb#1323)
* Release notes for AQL graph traversal tracing * Feedback --------- Co-authored-by: Paula Mihu <97217318+nerpaula@users.noreply.github.com>
1 parent d00e374 commit 192c921

File tree

2 files changed

+24
-0
lines changed

2 files changed

+24
-0
lines changed

3.11/release-notes-api-changes311.md

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -57,6 +57,12 @@ value of `0` as the `numberOfShards`. They now return the actual number of
5757
shards. This value can be higher than the configured `numberOfShards` value of
5858
the graph due to internally used hidden collections.
5959

60+
#### Log API
61+
62+
Setting the log level for the `graphs` log topic to `TRACE` now logs detailed
63+
information about AQL graph traversals and (shortest) path searches.
64+
Some new log messages are also logged for the `DEBUG` level.
65+
6066
### Privilege changes
6167

6268

3.11/release-notes-new-features311.md

Lines changed: 18 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -233,3 +233,21 @@ You can configure the feature via the following new startup options:
233233
Note that an auto-flush is only executed if the number of live WAL files
234234
exceeds the configured threshold and the last auto-flush is longer ago than
235235
the configured auto-flush check interval. This avoids too frequent auto-flushes.
236+
237+
## Miscellaneous changes
238+
239+
### Trace logs for graph traversals and path searches
240+
241+
Detailed information is now logged if you run AQL graph traversals
242+
or (shortest) path searches with AQL and set the
243+
log level to `TRACE` for the `graphs` log topic. This information is fairly
244+
low-level but can help to understand correctness and performance issues with
245+
traversal queries. There are also some new log messages for the `DEBUG` level.
246+
247+
To enable tracing for traversals and path searches at startup, you can set
248+
`--log.level graphs=trace`.
249+
250+
To enable or disable it at runtime, you can call the
251+
[`PUT /_admin/log/level`](http/monitoring.html#modify-and-return-the-current-server-log-level)
252+
endpoint of the HTTP API and set the log level using a request body like
253+
`{"graphs":"TRACE"}`.

0 commit comments

Comments
 (0)
0