Skip to content

Commit 1501cf1

Browse files
committed
Updated table to HTML
1 parent 69177a7 commit 1501cf1

File tree

1 file changed

+17
-11
lines changed

1 file changed

+17
-11
lines changed

_gsocblogs/2025/blog_Intelligent_Logging_Pipeline_OsamaTahir.md

Lines changed: 17 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -74,27 +74,33 @@ Suppose a log system has several events, each represented by a unique ID. The mo
7474
</p>
7575

7676
<div style="text-align: center;">
77-
<table style="border-collapse: collapse; margin: auto; text-align: center; width: 60%;">
77+
<table style="
78+
border-collapse: collapse;
79+
margin: auto;
80+
width: 60%;
81+
font-family: system-ui, -apple-system, 'Segoe UI', Roboto, sans-serif;
82+
font-size: 16px;
83+
text-align: center;
84+
">
7885
<thead>
79-
<tr>
80-
<th style="border-bottom: 2px solid #444; padding: 8px 20px;">Unique ID</th>
81-
<th style="border-bottom: 2px solid #444; padding: 8px 20px;">Event</th>
82-
<th style="border-bottom: 2px solid #444; padding: 8px 20px;">Probability</th>
86+
<tr style="border-bottom: 2px solid #444; border-top: 2px solid #444;">
87+
<th style="padding: 8px 60px;">Unique ID</th>
88+
<th style="padding: 8px 60px;">Event</th>
89+
<th style="padding: 8px 60px;">Probability</th>
8390
</tr>
8491
</thead>
8592
<tbody>
86-
<tr><td style="padding: 6px 20px;">0</td><td style="padding: 6px 20px;">Login</td><td style="padding: 6px 20px;">0.7</td></tr>
87-
<tr><td style="padding: 6px 20px;">1</td><td style="padding: 6px 20px;">Upload File</td><td style="padding: 6px 20px;">0.4</td></tr>
88-
<tr><td style="padding: 6px 20px;">2</td><td style="padding: 6px 20px;">Select File</td><td style="padding: 6px 20px;">0.6</td></tr>
89-
<tr><td style="padding: 6px 20px;">3</td><td style="padding: 6px 20px;">Logout</td><td style="padding: 6px 20px;">0.25</td></tr>
90-
<tr><td style="padding: 6px 20px;">4</td><td style="padding: 6px 20px;">Submit File</td><td style="padding: 6px 20px;">0.3</td></tr>
93+
<tr><td style="padding: 8px 20px;">0</td><td style="padding: 8px 20px;">Login</td><td style="padding: 8px 20px;">0.7</td></tr>
94+
<tr><td style="padding: 8px 20px;">1</td><td style="padding: 8px 20px;">Upload File</td><td style="padding: 8px 20px;">0.4</td></tr>
95+
<tr><td style="padding: 8px 20px;">2</td><td style="padding: 8px 20px;">Select File</td><td style="padding: 8px 20px;">0.6</td></tr>
96+
<tr><td style="padding: 8px 20px;">3</td><td style="padding: 8px 20px;">Logout</td><td style="padding: 8px 20px;">0.25</td></tr>
97+
<tr><td style="padding: 8px 20px;">4</td><td style="padding: 8px 20px;">Submit File</td><td style="padding: 8px 20px;">0.3</td></tr>
9198
</tbody>
9299
</table>
93100
<p style="font-style: italic; margin-top: 6px;">Table 1: Set of Events</p>
94101
</div>
95102

96103

97-
98104
<p align="justify">
99105
Here the model thinks "Login" is most likely next event, then "Select File" and then "Upload File" etc. Hence, the sequence will be [Login, Select File, Upload File, Submit File, Logout] and with their respective unique IDs, it will be [0, 2, 1, 4, 3]. With k=2, the model predicts the top 2 event IDs as [Login, Select File], while the true event is Upload File. Since the true event does not appear in the top 2 predictions, this case is flagged as an anomaly. When k=3, the top 3 event IDs are [Login, Select File, Upload File], and the true event Upload File is included, so it is considered normal. In practice, the model checks whether the true event ID appears within the top-k predicted IDs: if the true event is not present, the sequence is labelled as an anomaly; otherwise, it is treated as normal.
100106
</p>

0 commit comments

Comments
 (0)