Skip to content
This repository has been archived by the owner on Mar 1, 2024. It is now read-only.

Add option to force a request trace in Fly instrumentation tools #16

Closed
jsierles opened this issue Jun 1, 2022 · 4 comments
Closed

Add option to force a request trace in Fly instrumentation tools #16

jsierles opened this issue Jun 1, 2022 · 4 comments

Comments

@jsierles
Copy link
Collaborator

jsierles commented Jun 1, 2022

Graphql accepts the Fly-Force-Trace header. The REST API may support this later.
@DAlperin
Copy link
Member

DAlperin commented Jun 2, 2022

Should this be per resource or can I make it a provider wide flag?

@jsierles
Copy link
Collaborator Author

jsierles commented Jun 2, 2022

I think provider-wide, but off by default. Using this option should also output a useful warning so people don't leave it on all the time. We may also want to display debug info like the Fly-Request-ID returned from the API.

@DAlperin
Copy link
Member

DAlperin commented Jun 3, 2022

Would an environment variable do? FLY_DEVELOPER_MODE or some such?

@jsierles
Copy link
Collaborator Author

jsierles commented Jun 3, 2022

DEBUG would be good!

zxaos pushed a commit that referenced this issue Jun 6, 2023
@DAlperin
Add an API debug mode
af0abe0 
Closes #16
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@jsierles @DAlperin