missing field `self_times_ns` at line 1 column 563

[zKoz210]

Self-Hosted Version

25.10.0

CPU Architecture

x86_64

Docker Version

Docker version 28.5.1, build e180ab8

Docker Compose Version

Docker Compose version v2.40.1

Machine Specification

• My system meets the minimum system requirements of Sentry

Steps to Reproduce

Install 25.10.0 from 25.8.0

Expected Result

Actual Result

snuba-profiling-functions-consumer-1                         | {"timestamp":"2025-10-22T18:19:10.636934Z","level":"ERROR","fields":{"message":"Validation error","error":"Invalid message"},"target":"rust_snuba::strategies::processor","span":{"name":"_validate_schema"},"spans":[{"name":"_validate_schema"}]}
snuba-profiling-functions-consumer-1                         | {"timestamp":"2025-10-22T18:19:10.637050Z","level":"ERROR","fields":{"message":"Failed processing message","error":"missing field `self_times_ns` at line 1 column 563"},"target":"rust_snuba::strategies::processor"}

snuba-profiling-functions-consumer-1                         | {"timestamp":"2025-10-22T18:19:11.636930Z","level":"ERROR","fields":{"message":"Invalid message, but no DLQ policy configured","e":"InvalidMessage { partition: Partition { topic: Topic(\"profiles-call-tree\"), index: 0 }, offset: 1543574 }"},"target":"sentry_arroyo::processing"}

Event ID

No response

[gstorme]

Same here, seeing this log event about every 1s:

{"timestamp":"2025-10-22T20:31:37.037208Z","level":"ERROR","fields":{"message":"Failed processing message","error":"missing field `self_times_ns` at line 1 column 255"},"target":"rust_snuba::strategies::processor"}
{"timestamp":"2025-10-22T20:31:35.803723Z","level":"ERROR","fields":{"message":"Failed processing message","error":"missing field `self_times_ns` at line 1 column 273"},"target":"rust_snuba::strategies::processor"}
{"timestamp":"2025-10-22T20:31:34.700309Z","level":"ERROR","fields":{"message":"Failed processing message","error":"missing field `self_times_ns` at line 1 column 292"},"target":"rust_snuba::strategies::processor"}

[klemen-df]

same

[aldy505]

Asking this internally, probably we have a misconfiguration somewhere.

[aldy505]

Okay heard back from the internal Slack.

TLDR: Please enable these feature flags on your sentry/sentry.conf.py:

• projects:continuous-profiling-vroomrs-processing
• projects:transaction-profiling-vroomrs-processing

Then re-run ./install.sh

Long answer copied from Slack:

On Sept. 18th this PR removed the self_times array from the functions we send over (in vroom), hence why we're getting that error.

As a quick fix, you could enable the projects:continuous-profiling-vroomrs-processing and projects:transaction-profiling-vroomrs-processing feature flags.
This will enable the processing of the profiles directly in sentry instead of passing through vroom and it's what's already running in prod.
In future releases, you won't even need to enable them since, at this point, I think we can simply remove those feature flags.