docs: Clarify interactive logging TTL behavior

PiperOrigin-RevId: 485069403
googleapis · Oct 31, 2022 · 63cd62a · 63cd62a
1 parent 1330126
commit 63cd62a
Show file tree

Hide file tree

Showing 2 changed files with 4 additions and 6 deletions.
diff --git a/google/cloud/dialogflow/cx/v3beta1/advanced_settings.proto b/google/cloud/dialogflow/cx/v3beta1/advanced_settings.proto
@@ -16,6 +16,7 @@ syntax = "proto3";
 
 package google.cloud.dialogflow.cx.v3beta1;
 
+import "google/api/field_behavior.proto";
 
 option cc_enable_arenas = true;
 option csharp_namespace = "Google.Cloud.Dialogflow.Cx.V3Beta1";

diff --git a/google/cloud/dialogflow/cx/v3beta1/security_settings.proto b/google/cloud/dialogflow/cx/v3beta1/security_settings.proto
@@ -326,12 +326,9 @@ message SecuritySettings {
     // Retains data in interaction logging for the specified number of days.
     // This does not apply to Cloud logging, which is owned by the user - not
     // Dialogflow.
-    // User must set a value lower than Dialogflow's default 365d TTL. Setting a
-    // value higher than that has no effect.
-    // A missing value or setting to 0 also means we use Dialogflow's default
-    // TTL.
-    // Note: Interaction logging is a limited access feature. Talk to your
-    // Google representative to check availability for you.
+    // User must set a value lower than Dialogflow's default 365d TTL (time to
+    // live). Setting a value higher than that has no effect. A missing value or
+    // setting to 0 also means we use Dialogflow's default TTL.
     int32 retention_window_days = 6;
   }