Skip to content
This repository was archived by the owner on Aug 14, 2024. It is now read-only.
This repository was archived by the owner on Aug 14, 2024. It is now read-only.

Document in SDK Expected Features the HTTP integrations #254

@bruno-garcia

Description

@bruno-garcia

In SDK Expected Features we need some guideline of what we expect from integrating with HTTP clients in SDKs, when that's possible.

For example:

  • Add a breadcrumb to the Scope (so error events show that request)
    • Mention the breadcrumb categories and types that make sense here. Include HTTP status.
    • category could be the name of the HTTP integration. Type is http. Docs
  • Get some metrics (that for now can go as breadcrumb.data Example: bytes In, Bytes Out).
  • Should the SDK raise an event if a 5xx comes? If so what contexts.. If not, how does it propagate context upstream?

If Performance Monitoring is supported by the SDK:

  • Create a Span, child to the current Span bound to the Hub
  • Finish the span as success or failure depending on response HTTP status (500 is a failed Span)
    • We need to align/discuss 4xx and other status code range.
  • Include sentry-trace id to propagate a transaction downstream. Link to specific docs.

Link to some examples:

.NET
Java
Python

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions