Highlight searched value in logs

[nityanandagohain]

When something is searched, it should be highlighted in the logs.

[nityanandagohain]

@ankitnayan to have a scope here.

We are highlighting text in the log body if it's a full-text search. Else if it's a selected field in the filter then the selected field is highlighted in the log (the field won't be highlighted in raw view as it is not displayed).

let me know if there are any thoughts.

[ankitnayan]

That should be fine. The selected fields are removed from the body?

[nityanandagohain]

yes depends on the case, ex- k8s_namespace_name is not a part of log body.

[ankitnayan]

hmm... not keeping k8s_namespace_name in the body makes sense? When is a selected field kept in the body then?

[nityanandagohain]

any kind of field is present again in the body if the user has not cleaned up the body after extracting the attributes.

But it also depends on the user and the logs that they are printing.

Ex 1:-

{"ts": "1000...", "level":"info", "message":"this is my log"}

is parsed to

{
"ts": "1000...",
"body": "this is my log",
"attributes": {
   "level": "info"
  .....
 }
}

So in this case the body doesn't contain any attributes and is properly cleaned up.

Ex 2:-

{"ts": "1000...", "level":"asdasd", "message":"this is my log"}

is parsed to

{
"ts": "1000...",
"body": "{"ts": "1000...", "level":"info", "message":"this is my log"}",
"attributes": {
   "level": "info"
  .....
 }
}

In this case, the body is not cleaned up.

So actually it depends on the user how they are keeping it. But ideally it should be ex 1

[pranay01]

@palashgdev Can you also share a note on what input you need from me on this?

[nityanandagohain]

Will prioritise this is the next sprint.