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

studio: Schema reporting #70

Closed
Tracked by #66
abernix opened this issue Jul 7, 2021 · 1 comment
Closed
Tracked by #66

studio: Schema reporting #70

abernix opened this issue Jul 7, 2021 · 1 comment
Labels
component/studio-reporting Studio and GraphOS Metric Reporting (not analytics, but Studio usage)

Comments

@abernix
Copy link
Member

abernix commented Jul 7, 2021

Requirements

We need to be able to report the currently active schema to Apollo Studio. There's some existing art and a TypeScript reference implementation to follow along with here, so might be worth looking at, e.g., apollographql/apollo-server#5187 for inspiration and talking points in building out the design.

@o0Ignition0o o0Ignition0o transferred this issue from another repository Nov 4, 2021
@Geal Geal mentioned this issue Nov 10, 2021
5 tasks
@abernix abernix added the component/studio-reporting Studio and GraphOS Metric Reporting (not analytics, but Studio usage) label Mar 22, 2022
@abernix abernix changed the title Schema reporting studio: Schema reporting Mar 23, 2022
@abernix
Copy link
Member Author

abernix commented Jul 26, 2022

This has been deferred for a while, so let's close this for now and re-open this if we decide that we need to tackle it again. We do believe we want to do this, but it's not received a lot of traction yet, and I don't think the Gateway supports it.

@abernix abernix closed this as not planned Won't fix, can't repro, duplicate, stale Jul 26, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component/studio-reporting Studio and GraphOS Metric Reporting (not analytics, but Studio usage)
Projects
None yet
Development

No branches or pull requests

1 participant