Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

how to get X-Vcap-Request-Id (unique id generated for each cloud_controller interaction) #981

Closed
parasuram-tanguturu opened this issue Aug 2, 2019 · 3 comments

Comments

@parasuram-tanguturu
Copy link

how to get X-Vcap-Request-Id (unique id for generated for each cloud_controller interaction) ?
image

@parasuram-tanguturu parasuram-tanguturu changed the title how to get X-Vcap-Request-Id (unique id for generated for each cloud_controller interaction) how to get X-Vcap-Request-Id (unique id generated for each cloud_controller interaction) Aug 2, 2019
@sms0070
Copy link

sms0070 commented Jun 8, 2020

Is this possible or needs to be contributed?

@twoseat
Copy link
Contributor

twoseat commented Jun 8, 2020

Can you explain the business case for it? At the operations level we could generate dozens of interactions for a single transaction, and I can't immediately picture what reporting each of those would look like.

@sms0070
Copy link

sms0070 commented Jun 9, 2020

Hi @twoseat,

We have the following setup in our organisation.

one team(CF team) is responsible for developing of cf related stuff. Creation of services, launching of applications.

other team(mine) works on applications that communicate with CF team's product. We use cf-Java-client.

Now, for quite some time we've been experiencing issues with CF team regarding slow service creation, APIs returning 5xx responses.

However, since the number of calls is very high, they need either X-Vcap-Request-id or the timestamp at which the exact CF api call was made to track down the request.

This has become a bottleneck in all our communications with the CF team. That's why wanted to check here if it's possible to get the same.

@twoseat twoseat added this to the 3.25.0.RELEASE milestone Jun 29, 2020
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants