wso2 / wso2/api-platform

[Bug]: Analytics send_request_body and send_response_body deprecated

Open
#3,166 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Aspect/Configuration Severity/Critical Type/Bug
Dominant language
Go
Stars
71
Forks
111
Avg merge
1d 14h
Merged PRs (30d)
110

Description

Please select the area the issue is related to

Gateway

Please select the aspect the issue is related to

Aspect/Configuration (Config files, settings, env vars, defaults)

Description

send_request_body and send_response_body deprecated.

[analytics]
enabled = true
# Deprecated: allow_payloads is preserved for backward compatibility. When true
# and both send_request_body and send_response_body are false, both directions
# are enabled (bool fields cannot distinguish "unset" from explicitly false).
# To disable payloads entirely, set allow_payloads = false or remove it; do not
# rely on send_*_body = false while allow_payloads remains true.
allow_payloads = false
# Deprecated: send_request_body / send_response_body are preserved
# for backward compatibility and are mapped onto the [collector] body-capture flags
# during validation (with a warning). Prefer setting [collector] directly.
send_request_body = false
send_response_body = false
enabled_publishers = ["moesif"]

Request/Response body is true in colllector because, I need to log paylods in traffic logging.
The requirement is log paylods in traffic loggin while stop sending payload for Analytics.

Steps to Reproduce

Configure the gateway

[analytics]
enabled = true
enabled_publishers = ["moesif"]
send_request_body = false
send_response_body = false

[analytics.publishers.moesif]
application_id = '***'

[collector]
request_body = true
response_body = true
request_headers = true
response_headers = true

Deploy an LLM Provider.
Invoke it.

Payloads are publised.

Image
Severity Level of the Issue

Severity/Critical (Core functionality is broken but there is a workaround. Need urgent attention)

Environment Details (with versions)

API Platform 1.2.0

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing validation and handling for the [analytics] send_request_body and send_response_body settings alongside the [collector] body-capture settings. Reproduce the supplied configuration and verify that collector traffic logging still records payloads while the analytics publisher sends no request or response payloads.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
api, backend, observability
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
52/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.