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

[gateway] Add a transaction-id value for each request #307

Closed
brasseld opened this Issue Nov 9, 2016 · 3 comments

Comments

Projects
None yet
2 participants
@brasseld
Member

brasseld commented Nov 9, 2016

Currently a unique ID is generated for each incoming HTTP request.

The goal of this issue is to implement a transaction ID and propagate it to backends to track calls between the gateway and backends.

Basically, a new X-Gravitee-Transaction-Id will be forwarded to outgoing requests. This header may be overrided in the gateway configuration (gravitee.yml)

@brasseld brasseld added this to the 1.1.0 milestone Nov 9, 2016

@NicolasGeraud

This comment has been minimized.

Member

NicolasGeraud commented Nov 9, 2016

this id must be logged everytime it's possible, and if the incoming request already have a TransactionID, we have to use it instead of regenerate a new one

@brasseld

This comment has been minimized.

Member

brasseld commented Nov 10, 2016

@NicolasGeraud we're never logging anything from inbound / outbound requests for performance reason so not sur what to do with this id must be logged everytime it's possible.

But this transaction ID will be part of our reporting (Elastic / accesslog).

@NicolasGeraud

This comment has been minimized.

Member

NicolasGeraud commented Nov 10, 2016

I don't know where we log the requestID (perhaps when we throw exceptions) but we have to also log the transactionID at the same time.

brasseld added a commit to gravitee-io/gravitee-gateway-api that referenced this issue Nov 10, 2016

brasseld added a commit to gravitee-io/gravitee-gateway that referenced this issue Nov 10, 2016

brasseld added a commit to gravitee-io/gravitee-reporter-api that referenced this issue Nov 10, 2016

brasseld added a commit to gravitee-io-community/gravitee-reporter-elasticsearch that referenced this issue Nov 10, 2016

brasseld added a commit to gravitee-io/gravitee-reporter-file that referenced this issue Nov 10, 2016

@brasseld brasseld self-assigned this Nov 10, 2016

brasseld added a commit to gravitee-io/gravitee-gateway-api that referenced this issue Nov 10, 2016

brasseld added a commit to gravitee-io/gravitee-gateway that referenced this issue Nov 10, 2016

brasseld added a commit to gravitee-io/gravitee-reporter-api that referenced this issue Nov 18, 2016

brasseld added a commit to gravitee-io-community/gravitee-reporter-elasticsearch that referenced this issue Nov 18, 2016

brasseld added a commit to gravitee-io/gravitee-reporter-file that referenced this issue Nov 18, 2016

brasseld added a commit to gravitee-io/gravitee-gateway that referenced this issue Nov 18, 2016

brasseld added a commit to gravitee-io/gravitee-gateway that referenced this issue Nov 18, 2016

brasseld added a commit to gravitee-io/gravitee-gateway that referenced this issue Nov 18, 2016

NicolasGeraud added a commit to gravitee-io/gravitee-gateway that referenced this issue Nov 18, 2016

NicolasGeraud added a commit to gravitee-io/gravitee-gateway-api that referenced this issue Nov 18, 2016

NicolasGeraud added a commit to gravitee-io/gravitee-reporter-api that referenced this issue Nov 18, 2016

NicolasGeraud added a commit to gravitee-io-community/gravitee-reporter-elasticsearch that referenced this issue Nov 18, 2016

NicolasGeraud added a commit to gravitee-io/gravitee-reporter-file that referenced this issue Nov 18, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment