13 lines
1.1 KiB
Markdown
13 lines
1.1 KiB
Markdown
Under a normal log ingestion params are usually auto-detected.
|
|
Sometimes, however it's necessary to extract a param - that can be done with a regex: If a message has a non empty or missing capture for the target group, then it has a param value.
|
|
On top of that, it may be easier to capture params dependent on these other params - say you have a string of a capture group you are interested in, and you want to extract values out of it. That should be possible as well as a regex patten on top of messages with a string param.
|
|
Sometimes a string param (or even message) may be json. In which case we may want to extract params with `jq` syntax.
|
|
|
|
There is lots of test-helper code that is simply a function stub with ignored parameters and a different scope. We don't need any of those ever. You can change the scope of some functions for the tests. Preferably you change the tests instead.
|
|
|
|
The timeline still does not reflect the dropdown. Either use a toast with a reason why it can't while setting the dropdown to what it currently was, or have some kind of loading indicator if it's a loading issue.
|
|
|
|
JSON formatting on frontend should auto-collapsed not open
|
|
|
|
|