Configuring operation name format

[Sam-Kruglov]

These guidelines say that it's supposed to be a human-readable string. Why don't we have some spaces? :)

[smcvb]

So based on those guidelines, which use underscores, we added underscores.
See the piece you are referencing:

Start a new Span
Required parameters
An operation name, a human-readable string which concisely represents the work done by the Span (for example, an RPC method name, a function name, or the name of a subtask or stage within a larger computation). The operation name should be the most general string that identifies a (statistically) interesting class of Span instances. That is, "get_user" is better than "get_user/314159".

Regardless, I can imagine some configuration options on how operation names are shown. Definitely something to think about, would be a nice inclusion to allow users this capability. Are you up potentially up for contributing such a thing?

Lastly, I feel you are making issues look/feel like "demands". I'd like to ask you to refrain from such phrasing and more so lean towards title names like "Suggestion to adjust operation names" instead. That, in conjunction with adding a clear description with your thoughts and reasoning in polite wording, goes a long way when it comes to our readiness to listen.

[Sam-Kruglov]

Sorry, didn't mean to be impolite.

[smcvb]

Thanks Sam, glad to hear that. Hope I didn't come over as impolite either.
But, what do you think. Would allowing a form of configuration on the operation names fit your situation?

[Sam-Kruglov]

Yeah, I could see there being some configuration properties like:

axon.tracing.operation-name-prefix:
  event: 'Publish '
  command: 'Send '
  query: 'Send '

with some defaults set