Custom Columns #2487
-
|
When using Seq for analyzing data from multiple open telemetry resources it would be nice to immediately see that without having to open a log entry. It would really help us if one extra column would show:
Is that currently possible? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
|
Hi! Yes, this is possible currently. In the very top navigation bar, on the left, you should see a workspace name selected - by default, it's "Personal". 
On the Events screen, click the green tick mark next to This will create a signal in the right-hand-side signal bar. Give the signal a name like "OTel Columns" and save it. Drop down the workspace selector shown in that screenshot earlier and click the edit (pencil) icon. In there, you'll see "Default signals" - add your "OTel Columns" signal to the list, and save it. 🙌 |
Beta Was this translation helpful? Give feedback.
Hi! Yes, this is possible currently.
In the very top navigation bar, on the left, you should see a workspace name selected - by default, it's "Personal".
On the Events screen, click the green tick mark next to
service.nameon a log event, and choose "Show as column". Do the same forservice.instance.id.This will create a signal in the right-hand-side signal bar. Give the signal a name like "OTel Columns" and save it.
Drop down the workspace selector shown in that screenshot earlier and click the edit (pencil) icon.
In there, you'll see "Default signals" - add your "OTel Columns" signal to the list, and save it. 🙌