The traceid and spanid are not showing completely

[li-zheng-hao]

I am unable to view the complete trace ID and span ID in the logs on the dashboard page:

my configuration:

Log.Logger=new LoggerConfiguration()
    .WriteTo.Console()
    .WriteTo.Seq("http://localhost:5341")
    .CreateLogger();
builder.Host.UseSerilog();

builder.Services.AddOpenTelemetry()
    .ConfigureResource(r => r.AddService(GlobalSystem.ServiceName))
    .WithTracing(tracing =>
    {
        tracing.AddSource(GlobalSystem.SourceName);
        tracing.AddAspNetCoreInstrumentation();
        tracing.AddHttpClientInstrumentation();
        tracing.AddOtlpExporter(opt =>
        {
            opt.Endpoint = new Uri("http://localhost:5341/ingest/otlp/v1/traces");
            opt.Protocol = OtlpExportProtocol.HttpProtobuf;
        });
    });

If I use OpenTelemetry Sdk, it works well, but I want to use serilog

Seq version : 2024.3.11547

[liammclennan]

Hi @li-zheng-hao

Can you please add a little more about what you are trying to do?

You can get the trace id and span id using the copy actions in the trace menu, or a query like select @TraceId, @SpanId from stream limit 10 .

[li-zheng-hao]

I think when the mouse hovers over the Traceid, it should show the full content, not the truncated content, it would be a better experience that way

[liammclennan]

Thanks. That does sound reasonable, but I'm trying to understand how you are trying to use it. How is the full id helpful? Or how is the shortened version inconvenient?

[li-zheng-hao]

For example, I want to find all logs with traceId abc123, and I know they were recorded in the last few minutes. I just need to click on the time filter on the page and set it to 5 minutes. If the page could display the complete traceId, I could quickly find what I need (just by scrolling). But now the traceId only shows abc..., which could be abc456, abc678 or other traceIds. I have to manually enter @traceid=abc123 in the search box and then click search button, which obviously takes more time.

[nblumhardt]

We're reconsidering how we handle trace/span columns; it's not certain yet where it'll land, but thanks for all the feedback either way! 👍

[li-zheng-hao]

Thanks for the work you guys do, seq is a great product and I hope it gets even better!