Is your feature request related to a problem? Please describe
The current LogSQL examples in the documentation cover basic usage but lack practical scenarios commonly encountered in production environments. Users often need examples for troubleshooting authentication issues, analyzing API errors, and investigating user-specific problems.
Describe the solution you'd like
Expand the LogSQL examples section to include practical use cases such as:
Filtering authentication errors (e.g., by status codes like 400 or 422).
Investigating specific HTTP methods (e.g., POST or PATCH) for a given user.
Tracking errors by user ID or other contextual fields like x-user-id.
Creating analytics and graphs (e.g., error rates by status code, client version, or endpoint).
Searching for users based on patterns (e.g., specific app versions or usernames).
These examples should demonstrate combining filters, unpacking JSON fields, and using statistical functions like rate() and quantile()
Describe alternatives you've considered
Manually testing LogSQL queries in a VictoriaLogs instance, but this is time-consuming and requires prior knowledge.
Relying on external blog posts or community examples, which may not be officially validated or up-to-date.
Additional information
The new examples should align with real-world troubleshooting workflows and include clear explanations of each query’s purpose. This will help users quickly adapt the queries to their own logging schemas and use cases.
Is your feature request related to a problem? Please describe
The current LogSQL examples in the documentation cover basic usage but lack practical scenarios commonly encountered in production environments. Users often need examples for troubleshooting authentication issues, analyzing API errors, and investigating user-specific problems.
Describe the solution you'd like
Expand the LogSQL examples section to include practical use cases such as:
Filtering authentication errors (e.g., by status codes like 400 or 422).
Investigating specific HTTP methods (e.g., POST or PATCH) for a given user.
Tracking errors by user ID or other contextual fields like x-user-id.
Creating analytics and graphs (e.g., error rates by status code, client version, or endpoint).
Searching for users based on patterns (e.g., specific app versions or usernames).
These examples should demonstrate combining filters, unpacking JSON fields, and using statistical functions like rate() and quantile()
Describe alternatives you've considered
Manually testing LogSQL queries in a VictoriaLogs instance, but this is time-consuming and requires prior knowledge.
Relying on external blog posts or community examples, which may not be officially validated or up-to-date.
Additional information
The new examples should align with real-world troubleshooting workflows and include clear explanations of each query’s purpose. This will help users quickly adapt the queries to their own logging schemas and use cases.