Skip to content

feat: Added restate docs#162

Open
praveen5959 wants to merge 2 commits into
mainfrom
restate
Open

feat: Added restate docs#162
praveen5959 wants to merge 2 commits into
mainfrom
restate

Conversation

@praveen5959

Copy link
Copy Markdown
Contributor

No description provided.

@vercel

vercel Bot commented Jun 25, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
docs Ready Ready Preview, Comment Jun 26, 2026 3:46pm

Request Review

### Traces (`restate-traces`)

Restate emits one trace per invocation. Spans cover the full invocation lifecycle:

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

since we guide to configures RESTATE_TRACING_ENDPOINT ... i think this section should describe the spans emitted by restate server tracing.

also the restate docs mention spans like ingress, invocation-start, invocation-attempt, and invocation-end, while things like ctx.run, calls and sleeps are recorded as events on the attempt span. https://docs.restate.dev/server/monitoring/tracing#understanding-traces

so if these current span names are from TS SDK/app-level instrumentation?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Yeah this was added in my TS app. Have updated docs but let me know if you want me to run again for updated screenshots

@yashdotrv yashdotrv Jun 26, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

like if its not too much of a work then yes... so that i will have an updated one :)


const provider = new LoggerProvider({
resource: resourceFromAttributes({ [ATTR_SERVICE_NAME]: "restate-service" }),
processors: [new BatchLogRecordProcessor(exporter)],

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

here we are using new BatchLogRecordProcessor(exporter) It might not work depending on the package version that a user are onto...

but the current otel js logs exporter uses new BatchLogRecordProcessor({ exporter: logExporter })

so should we update this ?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Added the severityText.

BatchLogRecordProcessor(exporter) stays as-is - v0.219.0 (latest stable) takes positional arg. The { exporter } object form is unreleased main-branch API, not applicable yet.

@yashdotrv

yashdotrv commented Jun 26, 2026

Copy link
Copy Markdown
Contributor

@praveen5959 the overall thing lgtm... however these are some points I wanted to ask for... if it works then maybe I should go on and make these changes and add the log and traces screenshot from the stagging.

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

Successfully merging this pull request may close these issues.

2 participants