[manerow]

Fixes #37265

Problem

Agents send their logs to /services/ingestionPipelines/logs/{fqn}/{runId}, and the SDK put the pipeline's fully qualified name into that URL as it was. A service or agent name may contain /, for example Snowflake : Product/Eng NA. That slash adds an extra path segment, so no route matches and the server answers 404.

Sending logs is best effort, so nothing reports the failure. The run finishes as a success and its logs are lost.

A ? or # in a name breaks the same way, because each one ends the URL path early.

What this PR changes

Every log call in the SDK now encodes the name with the existing quote helper, the same one the SDK already uses for entity lookups by name. The / is sent as %2F, and the server decodes it back to the real name.

Names with only letters, digits, dots and underscores produce the same URL as before.

What users will notice

Agents on a service whose name contains / now ship their logs, so the log viewer has something to show.

How it was tested

• Unit tests cover all six log calls with a name containing /, ?, #, %, quotes and spaces. They fail without this change.
• End to end with the real OpenMetadata client and StreamableLogHandler, in the same startup order as a workflow, on a real service named logslash : Product/Eng NA:
  • The old writer sent the raw slash and got a 404.
  • The new writer shipped its records with no failed posts, closed the run, and the lines showed up in the UI log viewer.
• Against the server's own log endpoint: the raw slash finds no route (404), and the encoded name reaches the write handler. That check used a pipeline that does not exist, so it proves routing only. The successful write above went through a separate log backend behind a load balancer, not the server's own log storage.

Not in this PR

Agents already deployed keep the old behaviour until they run an SDK with this change.

[github-actions]

✅ PR checks passed

The linked issue has a description and all required Shipping project fields set. Thanks!

[gitar-bot]

Code Review ✅ Approved

🟡 Medium risk · Encoding pipeline FQNs across log endpoints changes request routing; incompatible decoding could cause log delivery or retrieval to fail.

Encodes the pipeline FQN with the existing quote helper in all six SDK log calls, so names containing /, ?, #, %, quotes, or spaces no longer break the /services/ingestionPipelines/logs/{fqn}/{runId} route. No issues found.

Verification

Rules No rules evaluated

Functional validation Not enabled

Set up

Auto-approval Not enabled

Set up

_{For more verification details, comment gitar display:verbose.}

Options

Display: compact → Showing compact verification results.

Comment with these commands to change the behavior for this request:

Compact

gitar display:verbose

_{Was this helpful? React with 👍 / 👎 | Powered by Gitar — free for open source}

[sonarqubecloud]

Quality Gate passed for 'open-metadata-ingestion'

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
85.7% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud