Skip to content

No parameter filtering is implemented #526

Open
@tombruijn

Description

@tombruijn

The JavaScript package offers a Span.setParams function but no filterParameters option is implemented like in the other integrations.

We don't call setParams anywhere ourselves in the integration packages, so any params transmitted are user submitted.

  • Is the lack of parameter filtering intentional?
  • Do we require users to filter the parameters themselves before sending an error?

To do

If we are implementing something for this.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions