Provide a search interface for log events
See original GitHub issueI’m using the OpenTracing API to add baggage to spans, which has produced a trace with the following log:
It would be great to be able to search traces for these events in a similar way to how tags can be searched e.g. something like the following to allow the example trace to be retrieved: event:baggage key:req-id value:b5a0akvpjll153h06o1g
.
Issue Analytics
- State:
- Created 6 years ago
- Comments:6 (3 by maintainers)
Top Results From Across the Web
Search log data using filter patterns - Amazon CloudWatch Logs
Under Log events, enter the filter syntax to use. To search all log entries for a time range using the console. Open the...
Read more >When and how to search with Amazon CloudWatch Logs
Learn how to search with CloudWatch Logs in this tutorial. ... For example, AWS sends log events related to a Lambda function into...
Read more >Admin log events - Google Workspace Admin Help
Manage log event data · Manage search results column data · Export search result data · Export data to BigQuery · Create reporting...
Read more >Use Logs UI - New Relic Documentation
Explore your log data · 1. Go to the Logs UI. · 2. Look for patterns. · 3. Narrow your focus. · 4....
Read more >View logs by using the Logs Explorer - Google Cloud
The Log fields pane offers a high-level summary of logs data and provides a more efficient way to refine a query. It shows...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
you query them the same way as you would tags
event:baggage|key:req-id|value:b5a0akvpjll153h06o1g
@vprithvi thanks for your input - the above hint helped: the multi tag search now works when I select the appropriate root service!