You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello, dears!
Please, help me to understand the strange behaviour of Loki.
Describe the bug
Small query with construction <regexp + metadata + regexp> in Grafana Explore overloads RAM and CPU await
{application="app"} !~ "(?i)info" | filename = "E:/app/app.log" |~ "(?i)err"
Only construction <regexp + metadata + regexp> triggers this problem.
In addition, in scanario below didnt stops the overload:
Cancellation of query (by timeout or manually) in Grafana, then OOM kill of Loki container - its restarting with and overloading again
Hello, dears!
Please, help me to understand the strange behaviour of Loki.
Describe the bug
Small query with construction <regexp + metadata + regexp> in Grafana Explore overloads RAM and CPU await
{application="app"} !~ "(?i)info" | filename = "E:/app/app.log" |~ "(?i)err"
RAM:
CPU:
But, occured that constructions below:
works properly - without any overloads by RAM/CPU
Only construction <regexp + metadata + regexp> triggers this problem.
In addition, in scanario below didnt stops the overload:
Cancellation of query (by timeout or manually) in Grafana, then OOM kill of Loki container - its restarting with and overloading again
Helps only manual restart of Loki container
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Overload by RAM/CPU await
Environment:
The text was updated successfully, but these errors were encountered: