Problem validating JSON document against schema

[astropanic]

2018-05-07T15:44:25.647+0200    ERROR    [request]    beater/handlers.go:384    error handling request    {"request_id": "f0472126-608a-41b8-81fb-1741d457e632", "error": "Problem validating JSON document against schema: I[#] S[#] doesn't validate with \"transaction#\"\n  I[#/transactions/0/spans/1/context/db/statement] S[#/properties/transactions/items/properties/spans/items/properties/context/properties/db/properties/statement/type] expected string or null, but got object"}

How I should proceed with debugging to find out what the issue is?
What information should I attach?

[mikker]

Hi @astropanic ! Thanks for reporting this. What ORM are you using? Is this a Rails app? Are you using Sequel/Mongo/something else? And what version?

[astropanic]

Hi @mikker,

Plain Rails with ActiveRecord

[mikker]

Can I make you try running master? It should be fixed. At least the statements should be converted to strings before sending.

I haven't heard of you problem with running both NewRelic and ElasticAPM before (from your support forum post). Is this maybe related?

[mikker]

Bump. How do the statements look like if you run master?

[astropanic]

I can't issue test runs against our production setup. We don't run RPM on staging (to compare). I can install only release gems from rubygems.org due to our rubygems mirror implementation.

…

On Tue, May 15, 2018 at 2:14 PM, Mikkel Malmberg ***@***.***> wrote: Bump. How do the statements look like if you run master? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#111 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AACZ3Etc171jbpeM_mEOWNBCY3ySbmqrks5tysbCgaJpZM4T1Aq5> .

[mikker]

Hi again. There's a new version out you could try. Let me know how it works.

[steve21168]

I'm receiving this errors on 1.0.0.beta1 gem.

This is a Rails app using Active Record with Postgresql

From the app side the errors look like this:

apm-server's response: {"error":"Problem validating JSON document against schema: I[#] S[#] doesn't validate with \"transaction#\"\n I[#/transactions/0/spans/13/context/db/statement] S[#/properties/transactions/items/properties/spans/items/properties/context/properties/db/properties/statement/type] expected string or null, but got object"}

From the APM server side:

ERROR [request] beater/handlers.go:384 error handling request {"request_id": "60e2fc39-c2f4-43e1-992b-e3fea1741122", "error": "Problem validating JSON document against schema: I[#] S[#] doesn't validate with \"transaction#\"\n I[#/transactions/0/spans/13/context/db/statement] S[#/properties/transactions/items/properties/spans/items/properties/context/properties/db/properties/statement/type] expected string or null, but got object"}

[sandrew]

Same for me

[ElasticAPM] POST returned an unsuccessful status code (400)
[ElasticAPM] apm-server's response: {"error":"data validation error: Problem validating JSON document against schema: I[#] S[#] doesn't validate with \"transaction#\"\n  I[#/transactions/0/spans/10/context/db/statement] S[#/properties/transactions/items/properties/spans/items/properties/context/properties/db/properties/statement/type] expected string or null, but got object"}

apm-server 6.3.0 and agent 1.0.0.beta1 and Rails 5.1.6

[mikker]

Weird. Are any of you using the Elasticsearch gem?

[steve21168]

@mikker Yes we're using the Elasticsearch gem.

[mikker]

@steve21168 I think that might be it. Can I make you try with this?:

gem 'elastic-apm', git: 'https://github.com/elastic/apm-agent-ruby', branch: 'fix-es-spans'`

It's this one: #157

[steve21168]

@mikker Yeah I'll try that branch and get back to you.

[steve21168]

@mikker I think that did the trick. Thanks!

[mikker]

Perfect! Thank you for helping out – I'm merging it to master and releasing a beta2. And also making an issue for APM Server to accept objects as "db" statements.