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

Add basic check tracing doc #215

Merged
merged 4 commits into from
Apr 9, 2024
Merged

Add basic check tracing doc #215

merged 4 commits into from
Apr 9, 2024

Conversation

josephschorr
Copy link
Member

No description provided.

@josephschorr josephschorr requested a review from samkim March 14, 2024 15:48
Copy link

vercel bot commented Mar 14, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
docs ✅ Ready (Inspect) Visit Preview 💬 Add feedback Apr 9, 2024 8:39pm

@@ -1,5 +1,5 @@
import { Callout } from 'nextra/components'
import YouTube from 'react-youtube'
import { Callout } from "nextra/components";
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: single quotes for mdx files


SpiceDB supports tracing of check requests to view the path(s) taken to compute the result, as well as timing information.

This information is requested via a header (versions older than v1.31.0) or setting `with_tracing: true` (v1.31.0 or later), and
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Might be more clear to separate the info here into separate sections: Versions previous to v1.31.0 and versions v1.31.0 on

Also specify where to set with_tracing eg in the request body.

Comment on lines 95 to 102
### Versions older than v1.31.0

Request tracing information via a header and the information is found in the response footer as JSON.

### v1.31.0 or later

Request tracing information by setting `with_tracing: true` in the request message and the information is found in the response message.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it might be a better structure to the page if this just documents the v1.31 behavior with a warning about using the header for older versions rather than having two additional layers of nesting headings.

**Warning:**
Versions older than v1.31.0

Request tracing information via a header and the information will be found in the response footer as JSON.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nitpick: indent this too

@samkim samkim merged commit bf8cee2 into main Apr 9, 2024
9 checks passed
@samkim samkim deleted the check-tracing branch April 9, 2024 20:50
@github-actions github-actions bot locked and limited conversation to collaborators Apr 9, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants