Skip to content

docs(js): use supportedCategories for crons, MCP, and queues/caches pages #19505

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.

Sign up for GitHub

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

Open
mydea wants to merge 1 commit into from
Open

docs(js): use supportedCategories for crons, MCP, and queues/caches pages #19505

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
25 changes: 2 additions & 23 deletions docs/platforms/javascript/common/crons/index.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,29 +4,8 @@ sidebar_title: Crons
description: "Sentry Crons allows you to monitor the uptime and performance of any scheduled, recurring job in your application using the Sentry JavaScript SDK."
sidebar_order: 9
sidebar_section: features
supported:
- javascript.nextjs
- javascript.sveltekit
- javascript.remix
- javascript.react-router
- javascript.astro
- javascript.bun
- javascript.deno
- javascript.node
- javascript.eve
- javascript.mastra
- javascript.aws-lambda
- javascript.azure-functions
- javascript.connect
- javascript.express
- javascript.fastify
- javascript.gcp-functions
- javascript.hapi
- javascript.hono
- javascript.koa
- javascript.nestjs
- javascript.cloudflare
- javascript.nitro
supportedCategories:
- server
---

Once implemented, it'll allow you to get alerts and metrics to help you solve errors, detect timeouts, and prevent disruptions to your service.
Expand Down
25 changes: 2 additions & 23 deletions docs/platforms/javascript/common/crons/troubleshooting.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3,29 +3,8 @@ title: "Crons Troubleshooting"
sidebar_title: "Troubleshooting"
description: "Learn how to troubleshoot your Cron Monitoring setup."
sidebar_order: 9000
supported:
- javascript.nextjs
- javascript.sveltekit
- javascript.remix
- javascript.react-router
- javascript.astro
- javascript.bun
- javascript.deno
- javascript.node
- javascript.eve
- javascript.mastra
- javascript.aws-lambda
- javascript.azure-functions
- javascript.connect
- javascript.express
- javascript.fastify
- javascript.gcp-functions
- javascript.hapi
- javascript.hono
- javascript.koa
- javascript.nestjs
- javascript.cloudflare
- javascript.tanstackstart-react
supportedCategories:
- server
Comment on lines +6 to +7

@sentry sentry Bot Sep 18, 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.

Bug: Using supportedCategories: [server] hides documentation from platforms like AWS Lambda because their configs lack a categories field, causing the isSupported check to fail.
Severity: HIGH

Suggested Fix

To fix this, add the categories: [server] property to the config.yml files for all relevant serverless platforms (e.g., aws-lambda, azure-functions, gcp-functions). Alternatively, revert the front matter filtering on the affected pages to use the previous explicit supported list, or modify the isSupported function to handle missing categories.

Prompt for AI Agent 
Review the code at the location below. A potential bug has been identified by an AI
agent. Verify if this is a real issue. If it is, propose a fix; if not, explain why it's
not valid.

Location: docs/platforms/javascript/common/crons/troubleshooting.mdx#L6-L7

Potential issue: The change from an explicit `supported` list to `supportedCategories:
[server]` in the front matter of documentation pages introduces a bug. The `isSupported`
function in `frontmatter.ts` now checks if a platform's `categories` array includes
`'server'`. However, serverless platforms like `aws-lambda`, `azure-functions`, and
`gcp-functions` do not have a `categories` field defined in their `config.yml`. As a
result, the check fails, and these platforms are incorrectly excluded from seeing
relevant documentation pages, such as the crons documentation, despite being listed in
`<PlatformSection>` components on the page.

Also affects:

  • docs/platforms/javascript/common/crons/index.mdx:7~8

Did we get this right? 👍 / 👎 to inform future reviews.

---

<PlatformCategorySection supported={['server', 'serverless']}>
Expand Down
24 changes: 2 additions & 22 deletions docs/platforms/javascript/common/mcp-monitoring/index.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,28 +4,8 @@ sidebar_title: MCP Monitoring
sidebar_order: 8
sidebar_section: features
description: "Monitor MCP server tool executions, prompt retrievals, resource access, and errors."
supported:
- javascript.node
- javascript.aws-lambda
- javascript.azure-functions
- javascript.connect
- javascript.express
- javascript.fastify
- javascript.gcp-functions
- javascript.hapi
- javascript.hono
- javascript.koa
- javascript.nestjs
- javascript.bun
- javascript.deno
- javascript.nextjs
- javascript.nuxt
- javascript.astro
- javascript.solidstart
- javascript.sveltekit
- javascript.remix
- javascript.cloudflare
- javascript.tanstackstart-react
supportedCategories:
- server
---

With Sentry's [MCP Monitoring](/product/mcp-servers/), you can track and debug MCP servers with full-stack context. You can monitor tool executions, prompt retrievals, resource access, and error rates alongside your other Sentry data, including logs, errors, and traces.
Expand Down
26 changes: 2 additions & 24 deletions docs/platforms/javascript/common/tracing/instrumentation/caches-module.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,30 +2,8 @@
title: Instrument Caches
sidebar_order: 1000
description: "Learn how to manually instrument your code to use Sentry's Cache module."
supported:
- javascript.node
- javascript.eve
- javascript.mastra
- javascript.aws-lambda
- javascript.azure-functions
- javascript.connect
- javascript.express
- javascript.fastify
- javascript.gcp-functions
- javascript.hapi
- javascript.hono
- javascript.koa
- javascript.nestjs
- javascript.bun
- javascript.deno
- javascript.nextjs
- javascript.nuxt
- javascript.astro
- javascript.solidstart
- javascript.sveltekit
- javascript.remix
- javascript.cloudflare
- javascript.tanstackstart-react
supportedCategories:
- server
---

A cache can be used to speed up data retrieval, thereby improving application performance. Because instead of getting data from a potentially slow data layer, your application will be getting data from memory (in a best case scenario). Caching can speed up read-heavy workloads for applications like Q&A portals, gaming, media sharing, and social networking.
Expand Down
26 changes: 2 additions & 24 deletions docs/platforms/javascript/common/tracing/instrumentation/queues-module.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,30 +2,8 @@
title: Instrument Queues
description: "Learn how to manually instrument your code to use Sentry's Queues module"
sidebar_order: 20
supported:
- javascript.node
- javascript.eve
- javascript.mastra
- javascript.aws-lambda
- javascript.azure-functions
- javascript.connect
- javascript.express
- javascript.fastify
- javascript.gcp-functions
- javascript.hapi
- javascript.hono
- javascript.koa
- javascript.nestjs
- javascript.bun
- javascript.deno
- javascript.nextjs
- javascript.nuxt
- javascript.astro
- javascript.solidstart
- javascript.sveltekit
- javascript.remix
- javascript.cloudflare
- javascript.tanstackstart-react
supportedCategories:
- server
---

To ensure that you have performance data about your messaging queues, you'll need to instrument custom spans and transactions around your queue producers and consumers.
Expand Down
Loading