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

migration plan and guide from classic agent #267

Open
trentm opened this issue Jul 4, 2024 · 1 comment
Open

migration plan and guide from classic agent #267

trentm opened this issue Jul 4, 2024 · 1 comment
Assignees

Comments

@trentm
Copy link
Member

trentm commented Jul 4, 2024

Some customers will migrate from the classic agent (elastic-apm-node) and should have a guide on how to do so. This should cover:

  • equivalents (or close) for all classic agent config options, or a list of limitations and descriptions of impact
  • a comparison of which supported-tech is not currently supported in the new distro that is in https://www.elastic.co/guide/en/apm/agent/nodejs/current/supported-technologies.html This is mostly about instrumentations, but should also include things like Node.js versions (if different); diff in ESM support; special cases like Azure Functions, Lambda.
  • (stretch) some discussion of instrumentation differences for each significant instr

Part of preparing for this guide should result in issues being created for feature work that we can do to ease the migration.

@estolfo
Copy link

estolfo commented Sep 13, 2024

This blog post about the Go agent might be a useful reference.

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