Services that do not return X-Action-Name header have a single "No_controller_reached" endpoint in the UI about diffy HOT 4 CLOSED

please do

from diffy.

That approach would work as long as your URLs don't have any path params. Unfortunately, most (or at least enough) services do have path params in their URL structures. This leads to a very bad situation where almost every request ends up creating an endpoint and your UI gets cluttered with multiple endpoints that actually represent the same controller method.

One feature we would love to see is to do some cardinality analysis on the request URL patterns to dynamically identify path params without knowing anything about the target's internal controller routing logic. e.g.

/user/1/name
/user/2/name
/user/3/name
...
might then be automatically collapsed to a single endpoint represented by:

/user/:path_param1/name

Without the ability to collapse endpoints the user experience degenerates very quickly which is why for the time being we require either the request to have a "Canonical-Resource" header or the responses from the targets to have and "X-Action-Name" header.

from diffy.

I agree that my suggestion was far from ideal.

I suggested it because I thought this was a slightly better default. I think my main concern was that the displayed text No_controller_reached seemed to indicate some errors which was confusing to me. I noticed that the README was updated, but I wonder if No_controller_reached should be renamed to something like Undefined_endpoint or Unnamed_endpoint?

from diffy.

Agreed. Undefined_endpoint sounds like a better choice than No_controller_reached. Please feel free to do the honors.

from diffy.