You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After having attended Elastic APM workshop, it seems the community needs some help if we are to get our issues of defective Moovbox hardware resolved. So far we've tested the current 6.7.x branch of the parent fork and found it partially usable. Seems there has been lots of changes in the ELK API structure, including the deprecated aka deletedv1/transactions API endpoint.
|#217 - https://projects.vta.org/projects/rti-bounce-proxy/work_packages/251/activity
After having attended Elastic APM workshop, it seems the community needs some help if we are to get our issues of defective Moovbox hardware resolved. So far we've tested the current 6.7.x branch of the parent fork and found it partially usable. Seems there has been lots of changes in the ELK API structure, including the deprecated aka deleted
v1/transactions
API endpoint.So to make a v2 compatible APM agent, we need to send validated NDJSON based on Elastic's latest implementation standards and JSON schema documentation, please see example here @ https://www.elastic.co/guide/en/apm/server/7.0/metadata-api.html
docs/spec
JSON schema for validationjshint
validation script for sample data and JSON schemasThe text was updated successfully, but these errors were encountered: