Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

adapting an existing agent to apm-server #1426

Closed
WassimDhib opened this issue Oct 8, 2018 · 2 comments
Closed

adapting an existing agent to apm-server #1426

WassimDhib opened this issue Oct 8, 2018 · 2 comments

Comments

@WassimDhib
Copy link

Hi,

I'm running my own java agent on multiple applications. I actuallly send data to logstash and want to migrate to apm-server.

I noticed some differences between my data model and what the apm-server intake api (v1) allows .

The main differences are the ability to

  • send metrics and counters such as memory/cpu/jvm consumption
  • send spans independently from transaction (useful for very long transactions, or distributed tracing)
  • correlate server side transaction with end used (rum) transaction

My question is to know if the v2 api will support those features ?

@simitt
Copy link
Contributor

simitt commented Oct 15, 2018

v2 allows for sending spans separated from transactions. It also introduces a trace_id which can be used to link together transactions from different services. There are two meta issues describing changes in v2: #1237 and #1390.

There is an experimental endpoint for sending metrics already in v1.

You can also check out the official Java agent and the RUM agent.

@alvarolobato
Copy link

I'm closing this issue, let us know if you have any further questions. Also feel free to use the discuss APM forums to ask question https://discuss.elastic.co/c/apm

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants