feat: add guides for more otel collector use cases (#15680)
Added guides for utilizing the otel collector with AWS CloudWatch, Kafka, Nginx, syslog, and Windows events for common infra/applications.
Documentation Changelog
Track recent updates to Sentry docs
Update docs (#15701)
Updated data forwarding section in Sentry docs for Splunk.
feat: Doc on introducing breaking changes to SDKs (#15647)
Added a page to guide discussions on introducing breaking changes in SDKs, including examples, user experience impact, and tips for smoother transitions.
docs(dotnet): fix Blazor WebAssembly example (#15731)
Fixed issue in Sentry docs for Blazor WebAssembly example where methods `UseSentry` and `AddSentry` were not found due to missing or disabled `<ImplicitUsings>enable</ImplicitUsings>` in .csproj file.
feat(crons): Add missing .NET docs (#15697)
Added missing .NET docs for upsert and Heartbeat in dotnet.mdx for crons feature.
df docs (#15704)
Added data forwarding page under /organizations/integrations/data-forwarding in Sentry docs.
feat: Add docs about vercel drains via vercel marketplace integration (#15730)
Added documentation for log/trace drains with Vercel integration via Sentry Marketplace, detailed in index.mdx and vercel.mdx files.
docs(tanstackstart-react): Add source maps quickstart instructions (#15709)
Added source maps quickstart instructions for Tanstack Start React SDK in the Sentry documentation.
docs(sourceMaps): Add `filesToDeleteAfterUpload` when source maps are enabled (#15609)
Added `filesToDeleteAfterUpload` option in snippets with enabled source maps, now presented as a warning in Sentry docs.
fix(apple): Enhance GraphQL operation tracking documentation (#15716)
Enhanced documentation for GraphQL operation tracking in files graphql-operation-tracking.mdx, http-client-errors.mdx, and options.mdx to improve clarity and accuracy.
docs(js): update Solid quick start guide (#15644)
Updated Solid Quick Start guide in Sentry docs.
feat(spans): Document trace attachments (#15705)
Added documentation for trace attachments in spans to provide more context and information for users.
ref(metrics): add metric options for PHP (#15715)
Added metric options for PHP in the Sentry documentation.
feat(metrics): move PHP to list of supported SDKs (#15712)
Added PHP to the list of supported SDKs in Sentry to enhance monitoring capabilities for PHP applications.
feat(metrics): add documentation for metrics for laravel/symfony (#15694)
Added documentation for metrics for Laravel/Symfony due to different flushing behaviors compared to regular SDK, ensuring accurate usage.
update uptime ips url (#15722)
Updated the URL for uptime IPs in the ip-ranges.mdx file.
feat: add page for new web vitals performance issues (#15693)
Added new page for web vitals performance issues to provide guidance on monitoring and improving website performance.
refactor(crons): add SentryCron decorator documentation (#15682)
Sentry docs now include a new include file for SentryCron decorator details, improving organization and maintainability.
feat(AI): Add AI Agent Monitoring documentation for .NET `Microsoft.Extensions.AI` (#15431)
Added AI Agent Monitoring documentation for .NET `Microsoft.Extensions.AI` in Sentry docs.
chore(dynamic-sampling): add notice that we will remove the get samples button (#15710)
Removed the Get Samples button in Sentry docs to align with the move to Span First, updating index.mdx file accordingly.
Showing the 20 most recent updates. View the full content dashboard or subscribe to the RSS feed.
- Full Content Dashboard - View all Sentry content (blog, videos, docs, changelog)
- RSS Feed - Subscribe to doc updates in your RSS reader
- JSON API - Programmatically access changelog data
The changelog updates automatically throughout the day. Summaries are generated by AI to provide quick, user-friendly insights into each update from the getsentry/sentry-docs repository.
Was this helpful?
Help improve this content
Our documentation is open source and available on GitHub. Your contributions are welcome, whether fixing a typo (drat!) or suggesting an update ("yeah, this would be better").
Our documentation is open source and available on GitHub. Your contributions are welcome, whether fixing a typo (drat!) or suggesting an update ("yeah, this would be better").