Our current logging system has some limitations when parsing JSON-formatted log content. To improve the flexibility and efficiency of log parsing, we propose to add support for parsing nested fields within JSON logs and to allow the exclusion of unnecessary fields during the parsing process.
User Stories
As a developer, I want to parse JSON logs that contain nested structures so that I can accurately retrieve the data I need.
As a system administrator, I want to configure log parsing rules to ignore fields that are not necessary for the current system or application, thereby reducing processing time and storage space usage.
Expected Features
Add the capability to parse nested fields in JSON logs, allowing access to nested data based on specified paths.
Provide configuration options that let users define and exclude fields that are not required for parsing, to optimize performance and resource usage.
Use Cases
When dealing with log files that contain complex structures, such as user information or transaction details, being able to directly access deep data fields.
When log data includes sensitive information or useless data, being able to configure the exclusion of these fields to prevent unnecessary data leaks or interference.
Description
Our current logging system has some limitations when parsing JSON-formatted log content. To improve the flexibility and efficiency of log parsing, we propose to add support for parsing nested fields within JSON logs and to allow the exclusion of unnecessary fields during the parsing process.
User Stories
Expected Features
Use Cases