From a0afb0de6bb512fbcc98f128e78f9d4f24be9e4d Mon Sep 17 00:00:00 2001 From: Pedro Miola Date: Fri, 11 Apr 2025 13:49:44 -0300 Subject: [PATCH] =?UTF-8?q?(feat):=20add=20placeholders=20for=20request=20?= =?UTF-8?q?ID=20handling=20and=20examples=20in=20Real-Time=20Events=20docu?= =?UTF-8?q?mentation=20C=C3=B3digo:=2020501?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- .../real-time-events/analyze-logs/understand-logs.mdx | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/src/content/docs/en/pages/observe-journey/real-time-events/analyze-logs/understand-logs.mdx b/src/content/docs/en/pages/observe-journey/real-time-events/analyze-logs/understand-logs.mdx index 8ed4e711ae..0302fd289c 100644 --- a/src/content/docs/en/pages/observe-journey/real-time-events/analyze-logs/understand-logs.mdx +++ b/src/content/docs/en/pages/observe-journey/real-time-events/analyze-logs/understand-logs.mdx @@ -32,5 +32,7 @@ For example, if you notice your application isn't properly exhibiting what you c You can query a filtered search to receive specific variables and values according to what you're analyzing. This could be the ideal choice if you already know what type of information you're going to analyze. For example, if you suspect there may be malicious users trying to access your edge application, you can query the **Edge Applications** data source and analyze variables such as `$city`, `$host`, `$http_referrer`, `$remote_addr`, `$request_uri`, and so on. -

+-> [TECHWRITER TODO: (INSERT) (EXPLANATION OF HOW TO SEARCH FOR REQUEST ID WITHOUT THE -XXXX SUFFIX) ABOUT (REQUEST ID HANDLING IN REAL-TIME EVENTS AND GRAPHQL)] +-> [TECHWRITER TODO: (INSERT) (EXAMPLES OF QUERYING REQUEST IDs) ABOUT (USING REQUEST ID IN REAL-TIME EVENTS AND GRAPHQL)] +

\ No newline at end of file