|
|
|
|
|
|
by Topgamer7
808 days ago
|
|
|
I use LogQL a fair amount. Often times even just negative filtering is quite useful. I do a fair amount of tracking down of issues with LogQL. Looking for logs specific to a customer support ticket. Filtering for logs by a traceId for distributed traces. I have serious doubts this new UI is something I will care about at all. The explore ui for setting labels is atrocious and painful, and I'd rather just give me the text input for LogQL* *: Please FFS someone fix the Ctrl+f creating a vscode like find dialog that only finds inside the text input. I never want to do a find specifically isolated to my LogQL |
|
|
Quick update: that has been fixed and will be available in Grafana 11.1.