Closed marcnoon closed 1 week ago
Any datetime must represent a minimum, maximum, average, or any other value the client is interested in but is just a message_part. The GUID is simply a string representation of a GUID. It is also a message_part. The message will be repeated if one or more users or clients encounter the same conditions. The count refers to the frequency of a particular repeating message. The pattern represents how often a message repeats. I am primarily interested in the recurring parts of a message, so that is what will be counted. However, for now, everything will be based on message counts.
I might dumb this down for starting out and let the user simply use a code in regex for log files it is interested in and wants to be notified about and wants to keep track of things like the count.
We finished this issue, issue number 5, at least creating the model and verifying it works between the test.py server and the clients, both the client.py and the Angular client. So, the model is consistent between client and server, and we can complete that issue.
Completed
Model will contain things like new LogEntry { non_repeating_message_parts: array,
repeating_message: string,
repeating_message_count: int,
repeating_message_pattern: string
}
The count is the number of times the message occurs the pattern is the mathematical pattern as it relates to n log entries for the message that can repeat. The pattern is usually mathematical, like a summation math symbology that can be analyzed easily. The non_repeating_message_parts will be enclosed in brackets and be given a letter for each repeating entry Right now, it's just an idea floating around.