Add query log forwarding

Author: SeBBBe

modules/ROOT/pages/logging/log-forwarding.adoc

@@ -1,12 +1,15 @@
 [[aura-query-logs]]
-= Security log forwarding
+= Log forwarding
 :page-aliases: platform/logging/log-forwarding.adoc
 
 label:AuraDB-Business-Critical[]
 label:AuraDB-Virtual-Dedicated-Cloud[]
 label:AuraDS-Enterprise[]
 
-With security log forwarding, you can stream security logs directly to a cloud project owned by your organization, in real time.
+With log forwarding, you can stream logs directly to a cloud project owned by your organization, in real time. The following types of logs are available:
+
+* Security logs
+* Query logs
 
 [NOTE]
 ====
@@ -33,13 +36,7 @@ If no log forwarding process is set up, a button to do so is displayed in the ce
 
 [NOTE]
 ====
-Aura Database and Analytics services are business-critical for users.
-There are requests to introduce more capabilities enabling access to logs and metrics to derive actionable insights using your choice of monitoring platform.
-
-Aura has a strong roadmap of observability sharing features including security logs, query logs, and other capabilities.
-Many of these logs can be of significant size, hence *a new consumption-based billing model including cloud egress costs* will be introduced in the future.
-
-Security is of paramount importance, and therefore the security logs are initially available for free.
+Security is of paramount importance, and therefore the security logs are initially available for free. For query logs, a volume-based egress charge will apply. Please refer to your contract for details.
 ====
 
 The complete steps for setting up log forwarding depend on the chosen cloud provider.
@@ -51,13 +48,25 @@ Exhaustive instructions are provided in the wizard which appears by following th
 * label:AuraDB-Business-Critical[] A specific instance will have its logs forwarded.
 * label:AuraDB-Virtual-Dedicated-Cloud[] All instances in the selected region will have their logs forwarded.
 * label:AuraDS-Enterprise[] All instances in the selected region will have their logs forwarded.
+. Select the type of logs to forward: *Security logs* or *Query logs*.
+* For query logs, it is possible to apply certain filters to decrease the volume of forwarded data.
 . Follow the instructions specific to your cloud provider.
 
 [NOTE]
 ====
-Only one log forwarding configuration is permitted for each unique scope.
+Only one log forwarding configuration of each type is permitted for each unique scope.
 ====
 
+=== Query log filters
+
+To apply filters to query logs, expand the Filter section in the log forwarding configuration wizard.
+
+Neo4j queries produce two log entries—a start entry indicating that the query was started, and an end entry containing the result of the query execution.
+
+The option *Remove start entries* allows you to only forward the end entries, which is sufficient for most analytical use cases and cuts the egress volume by almost half.
+
+The *Include* dropdown selects whether to forward all queries, only successful queries, or only failed queries.
+
 == Output destination
 
 Log forwarding can forward logs to the log service of the same cloud provider as the monitored instance is located in.