Conversation
| This setting allows users to opt-in to the query log analyzer feature in their Fleet Manager deployments. For more information, see the xref:logging/query-log-analyzer.adoc[Query log analyzer documentation]. | ||
|
|
||
| * Minimum required Neo4j version: *2026.03* | ||
| * Required Neo4j edition: *Enterprise* |
There was a problem hiding this comment.
There are labels for AuraDB Enterprise etc in this repo. We should ask the docs team if it's possible to bring over some of the labels from the operations manual. Then we could replace the two lines above with labels, like:
[role=label--enterprise]
and
[label--new-2026.03]
There was a problem hiding this comment.
Good suggestion! I forgot that these exist as a thing in the docs but from what I can tell from my local testing, these to labels seem to already work out-of-the-box. I wonder if we could just add them to the PR and then see what the docs team say about them.
There was a problem hiding this comment.
Interesting, the enterprise tag works for me locally but it no longer works in the PR build of the docs. So I guess that would have to be brought over. I'll ask the docs team if that is okay.
There was a problem hiding this comment.
Looks like it works for me! Will still have to run it past them though.
There was a problem hiding this comment.
I see you pushed a fix commit 😄
There was a problem hiding this comment.
I had a chat about this yesterday with the aura-docs team but I'll send them a message to tell that it works and to ask if it is okay. At least both of these tags are in the style guide so they feel like they should be fine, but I'll make sure just in case.
…eased at the same time
|
This PR includes documentation updates Updated pages: |
AlexicaWright
left a comment
AlexicaWright
left a comment
There was a problem hiding this comment.
Some editorial and style suggestions.
As for the labels, I can't see why not.
|
|
||
| == Settings | ||
|
|
||
| In the *Settings* tab, you can view and change deployment settings. Changes should take effect almost instantly. |
There was a problem hiding this comment.
| In the *Settings* tab, you can view and change deployment settings. Changes should take effect almost instantly. | |
| In the *Settings* tab, you can view and change deployment settings. | |
| Changes should take effect almost instantly. |
| [role=label--enterprise-edition label--new-2026.03] | ||
| === Query log analyzer | ||
|
|
||
| This setting allows users to opt-in to the query log analyzer feature in their Fleet Manager deployments. For more information, see the xref:logging/query-log-analyzer.adoc[Query log analyzer documentation]. |
There was a problem hiding this comment.
| This setting allows users to opt-in to the query log analyzer feature in their Fleet Manager deployments. For more information, see the xref:logging/query-log-analyzer.adoc[Query log analyzer documentation]. | |
| This setting allows users to opt-in to the query log analyzer feature in their Fleet Manager deployments. | |
| For more information, see xref:logging/query-log-analyzer.adoc[Query log analyzer]. |
|
|
||
| [NOTE] | ||
| ==== | ||
| We will collect aggregated and obfuscated query logs which we will store and retain for up to 30 days. You need to enable log obfuscation on your Neo4j deployment to use this feature. |
There was a problem hiding this comment.
| We will collect aggregated and obfuscated query logs which we will store and retain for up to 30 days. You need to enable log obfuscation on your Neo4j deployment to use this feature. | |
| Aggregated and obfuscated query logs are collected and these are stored and retained for up to 30 days. | |
| You need to enable log obfuscation on your Neo4j deployment to use this feature. |
4 participants
Add documentation for Fleet Manager deployment settings
Part of NOM-421