https://openobserve.ai/ logo
Join Slack
Powered by
Hi... I have been away from oo for some time, with...
# openobserve
c
Hi... I have been away from oo for some time, with a 0.50.5 instance (OSS, postgres, s3, logs only) ticking over happily. I just tried upgrading it, to the latest minor version of each major version. 0.50.6 was fine. But with 0.60.5 I have a problem. Upgrade itself and querying seems flawless. But all ingest (using _json from vector) fails with HTTP 415 (unsupported media type). Nothing in the log files except the POST failing. I can't see anything relevant in the release notes. Was something deprecated, or tightened up on?
h
i didn't remember anything related to this. the _json API always work as same format.
what is the o2 server log report?
c
Aug 10 121851 oo openobserve[27014]: 2026-08-10T111851.488927446+00:00 INFO config:axummiddlewaresaccess log - "POST /oo/api/pe/journal/_json HTTP/1.1" 415 - "986" "-" "Vector/0.45.0 (aarch64-unknown-linux-gnu 063cabb 2025-02-24 145202.810034614)" 0.000
h
how is your vector config? can you also share that?
c
Sanitised vector for one stream. (Nothing changed - I just stopped vector during the oo upgrade, verified upgrade & query, then restarted vector):
sources: journal_source: type: "journald" transforms: journal_transform: inputs: [ "journal_source" ] type: "remap" source: | .host = "$SHORT_HOSTNAME" .@timestamp = del(.timestamp) sinks: journal_oo: inputs: [ "journal_transform" ] type: "http" uri: "n.n.n.n/oo/api/…/_json" method: "post" auth: strategy: "basic" user: "vector@xxx.xx" password: "xxx" compression: "zstd" encoding: codec: "json" timestamp_format: "rfc3339" healthcheck: enabled: false
h
can you try change 
zstd
to 
gzip
c
Ha! that works...
h
then we know the reason now, can you help create one issue for this? i will add 
zstd
support again.
c
will do... when i remember how 🙂
👍 1
my upgrade path is planned to be 0.60.5, 0.70.3, 0.80.3, 0.90.3, 0.91.5 ...... anything you can think of i should be careful of?
h
you are running with pg/s3/single node, it is fine. just do it.
c
excellent .... thank you
h
Recommend upgrade to v0.92.0
That is a big version.
c
ok.... it wasn't there when i planned this a few days ago.... will add that step too
h
i already created issue for this case.
3 Views
Open in Slack
PreviousNext
Powered by