Search all services

[ringerc]

Counterpart to backend ticket jaegertracing/jaeger#423

The webui does not presently permit a search to be run until a service is selected.

This is awkward; the UI must often be reloaded to see new services. More importantly it makes it impossible to search for a tag or span name across all services. This becomes especially important if you're sharding your services to deal with #38 .

On a related note, the field for the span type that appears once a service is selected doesn't seem to accept freeform entries; if you put something in that doesn't match its validation list, it'll ignore it and find all span types. That's confusing ui and impractical for users who may have lots of span types in a complex system.

[tiffon]

@ringerc, thanks for filing this.

Currently, the query service requires a service to be selected for every query. jaegertracing/jaeger#423 touches on this.

the field for the span type that appears once a service is selected

Are you referring to the service-operations, e.g. the second dropdown?

You're right, it doesn't allow freeform entries. Freeform text that doesn't match one of the options would return an empty result.

That's confusing ui and impractical for users who may have lots of span types in a complex system.

Sorry, I don't follow. I look at the UI everyday so I guess I'm used to it. How is not allowing freeform entry of values that wouldn't match anything confusing or impractical?

Two things worth noting about the list of operations:

• It filters the list as you type
• Formerly, it shows only the first 200 matching entries
  • This is resolved on jaegertracing/jaeger-ui master, but not yet released on the Jaeger docker images

[ringerc]

That's just it - 200 unique trace points in a service doesn't seem like that much. Won't the list get unwieldy? But mostly what's weird is that it *allows* freeform entry, but ignores the input if there's no match, so what you see in the field doesn't match what's searched for. It searches for whatever was last there before the non-matching entry was typed/pasted in. It's awkward UI rather than a serious issue. I'd argue that searching for an entry that doesn't match is exactly what it should do.

…

-- Craig Ringer http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services

[ringerc]

My response was somewhat muddled from an unrelated issue.

What I was trying to get at here is that if you have 4 top-level services "serviceA", "serviceB", etc, and some of them may generate some common span names, you can't search across all of them. You must select a service first, and search only within this service.

[skydoctor]

Wondering if there are any known ways to search across all services? This would be especially useful when searching for error tags to quickly highlight any traces which have errors.

[schoentoon]

Also interested in searching across all/multiple services, so I can easily link data together from points where I may know the tag but not necessarily the service name. As I see the tag blocked, what is this exactly blocked by? I see a link to jaegertracing/jaeger#423 in the comments, but that thread seems even more stale than this one unfortunately.

[yurishkuro]

@schoentoon I responded on jaegertracing/jaeger#423

[ronnathaniel]

+1

[alex-kormukhin]

This feature is stopper for us for migration from zipkin. Zipkin can find by tags across all services:

We use elasticsearch as storage backend.