victorialogs-query

To search VictoriaLogs logs, send curl requests to the /select/logsql/query endpoint using LogsQL syntax, including authentication headers and RFC3339 timestamps to retrieve filtered log search results.

Yes, you can discover non-stream fields, stream fields, list streams, and stream IDs by targeting endpoints like /select/logsql/field_names, /select/logsql/field_values, and /select/logsql/streams to understand log distributions across namespaces and pods.

You can calculate instant and range statistics by querying the /select/logsql/stats_query and /select/logsql/stats_query_range endpoints with curl, allowing you to monitor log volume trends across services over specified time intervals.

Yes, VictoriaLogs supports log hit analysis and faceting via the /select/logsql/hits and /select/logsql/facets endpoints, enabling you to analyze log distributions and extract insights across typical namespaces and pods.

Available endpoints include /select/logsql/query, /select/logsql/stats_query, /select/logsql/stats_query_range, /select/logsql/hits, /select/logsql/facets, /select/logsql/field_names, /select/logsql/field_values, /select/logsql/streams, and /select/logsql/stream_ids for comprehensive log search and discovery.

The best way to debug outages is using LogsQL queries against VictoriaLogs to search logs, run instant or range statistics, and filter results, verifying deployments and monitoring log volume trends across services directly via curl.