Star us on GitHub

Log Search Specification

Logs are broken down into two discrete concepts: messages and attributes. Given the following log:'Queried table', { table: 'users', query: 'hello', }),

The log message is Queried table and the attributes are table:users and query:hello.

Searching for logs

For general information on searching logs, check out our Search docs.

Default Key

The default key for log search is message. If you enter an expression without a key (graphql request) it will be used as the key for the expression (message="*graphql request*").

For example given the following log:"excluding session due to no user interaction events")

We can find this log by typing excluding session due to no user interaction events.

Autoinjected attributes

By default, Highlight's SDKs will autoinject attributes to provide additional context as well as assisting in linking sessions and errors to their respective logs.

code.filepathFile path emitting the log./build/backend/worker/worker.go
code.functionFunction emitting the*Worker).Start.func3
code.linenoLine number of the file where the log was emitted.20
environmentThe environment specified in the SDKproduction
levelThe log levelinfo
messageThe log messagepublic-graph graphql request failed
os.descriptionDescription of the operating systemAlpine Linux 3.17.2 (Linux 5.10.167-147.601.amzn2.aarch64 #1 SMP Tue Feb 14 21:50:23 UTC 2023 aarch64)
os.typeType of operating systemlinux
secure_session_idSession id that contains this logwh1jcuN5F9G6Ra5CKeCjdIk6Rbyd
service_nameName of the service specified in the SDKprivate-graph
service_versionVersion of the service specified in the SDKe1845285cb360410aee05c61dd0cc57f85afe6da
sourceBroad origin of the logbackend
span_idSpan id that contains this log528a54addf6f91cc
trace_idTrace id that contains this log7654ff38c4631d5a51b26f7e637eea3c
Helpful Tips

Use the secure_session_id EXISTS search to filter out all logs that are not tied to a session.