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
Explore Logs fails to parse fields from unstructured logs. Take nginx logs as an example, where no fields are available.
The pattern parser can really help to provide fields for such unstructured log lines.
By adding | pattern `<_> "<method> <_>` to nginx logs, for example, a user can get the HTTP method broken out into a new field.
Doing this with text selection in a log line, where a user selects the HTTP method, and we would offer a method to break that into a new field, would be a great addition to support more unstructured log lines.
The text was updated successfully, but these errors were encountered:
Explore Logs fails to parse fields from unstructured logs. Take nginx logs as an example, where no fields are available.
The pattern parser can really help to provide fields for such unstructured log lines.
By adding
| pattern `<_> "<method> <_>`
to nginx logs, for example, a user can get the HTTP method broken out into a new field.(source)
Doing this with text selection in a log line, where a user selects the HTTP method, and we would offer a method to break that into a new field, would be a great addition to support more unstructured log lines.
The text was updated successfully, but these errors were encountered: