-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for an UUID option as request-id #31
Labels
Comments
malud
added
enhancement
New feature or request
good first issue
Good for newcomers
hacktoberfest
labels
Sep 29, 2020
Hi, I can pick this up if this is still open |
cvhariharan
added a commit
to cvhariharan/couper
that referenced
this issue
Oct 18, 2020
cvhariharan
added a commit
to cvhariharan/couper
that referenced
this issue
Oct 18, 2020
malud
pushed a commit
that referenced
this issue
Oct 19, 2020
malud
added
documentation
Improvements or additions to documentation
theme/config
and removed
enhancement
New feature or request
good first issue
Good for newcomers
hacktoberfest
labels
Oct 19, 2020
malud
pushed a commit
that referenced
this issue
Oct 21, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Couper generates a unique request id with the help of https://github.com/rs/xid .
Some projects have a requirement of a real uuid which should be sent along with the request.
To provide a good log correlation, couper should be able to generate those via configuration.
The correct place for this would be the
settings
block within our couper configuration file.Default should be
common
which would be the current behaviour with thexid
package.If the user configure the value
uuid4
another generation method should be mapped to theuidFn
Field of theHTTPServer
struct.Since all
settings
are mapped toconfig/runtime/HTTPConfig
this one must be configurable viaCOUPER_REQUEST_ID_FORMAT
and command flag-request-id-format
.Depends on PR #29 due to the
settings
block.Pick a stable uuid package.
The text was updated successfully, but these errors were encountered: