Skip to content

Commit aacf368

Browse files
Update README.md
Co-authored-by: Andrii Dembitskyi <[email protected]>
1 parent 8778259 commit aacf368

File tree

1 file changed

+6
-1
lines changed

1 file changed

+6
-1
lines changed

README.md

Lines changed: 6 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -40,7 +40,12 @@ jaeger:
4040
4141
## Name generation options
4242
43-
You can specify just the suffix, if you name generator service is named as `jaeger.name.generator.*` or if you have any other naming scheme you can put the whole name into the configuration.
43+
You can configure custom name generators based on regular expression pattern, which will be evaluated for operation name.
44+
45+
Configuration for this feature looks like key-value list, where key - regexp pattern, value - custom name generator DI service id (see details below).
46+
47+
Name generator should implement an 'TODO' interface.
48+
As a custom name generator you can specify a full DI service id, or just the suffix if your name generator service is named as `jaeger.name.generator.*`.
4449
Keys are considered body of the regular expression pattern, do not put any modifiers (e.g. `/i`, `/g`) or slashes; `route` of the request or `name` of the command should match to use alternative generator.
4550
Expressions are checked top to bottom, if no match is found, default generator will be used
4651

0 commit comments

Comments
 (0)