Is your feature request related to a problem?
We are extensively using the Hug web framework in our organization. Since Hug is built on top of Falcon, we have been using the falcon-instrumentation library to instrument our applications. However, this approach results in spans that are difficult to interpret, as shown in the screenshot below:

Describe the solution you'd like
We believe that better instrumentation support for Hug can be achieved through one of the following options:

• Develop a dedicated hug-instrumentation library, which would be largely similar (about 90%) to the existing falcon-instrumentation .
• Create a hug-instrumentation library that depends on falcon-instrumentation and overrides some functions. However, this solution might be less maintainable and less readable.
• Introduce a configuration option in the falcon-instrumentation library that enhances its compatibility with Hug.

Additional context
I have not personally tried the Falcon framework to see how spans are named there, but I assume they are similar to those of other frameworks. I would appreciate any input from project contributors on this matter and am willing to explore the issue further. What are your thoughts on the best approach to improve OpenTelemetry instrumentation for the Hug web framework?