Skip to content
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

Cannot access timings #190

Open
anar-khalilov opened this issue Jan 25, 2023 · 3 comments
Open

Cannot access timings #190

anar-khalilov opened this issue Jan 25, 2023 · 3 comments

Comments

@anar-khalilov
Copy link
Contributor

We want to access timings as shown below but we couldn't find a way.
Can you provide a way to be able to measure performance by making these timings accessible somehow?

image

@LeonHuston
Copy link
Contributor

Hey there, if you supply a header in your request with the key ,values being X-Bramble-Debug: timing it will return you the timing values in the extensions field of the response.

You can see what other values you can request with that header here

@anar-khalilov
Copy link
Contributor Author

Yes, we set this header to "all".

Can you provide a concrete example on how to access these values not from the package but from outside as a consumer of this package? We tried many different methods to no avail.

If there is no such way, could you provide one?

@pkqk
Copy link
Member

pkqk commented Jan 30, 2023

Hi @anar-khalilov, I'm not sure what you mean by outside the package?

The timings are in the JSON body of the HTTP response.

{
    "data": "",
    "extensions": {
        "plan": "",
        "timings": {
            "execution": "194ms",
            "format": "0s",
            "merge": "0s"
        }
    }
}

So if your HTTP client lets you inspect the response at a higher level than the data key then they are there. It doesn't currently break the timings down by service or field though.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants