Please tell us a bit about your Go applications environment, with a focus on the applications you want to monitor. For questions about which platforms you are using, tick any that apply now, or are very likely to apply in the near future.

This question is about how you would prefer to instrument your application. Broadly, these are the options:

Manual:
We provide an API, and you make changes to your application. This gives you 100% control over how your program is instrumented, at the greatest cost to you.

Runtime:
We provide an agent (a separate process) which will dynamically instrument your program, inserting tracing calls at runtime. This will require some changes to how you deploy your application, but will require little to no code changes.

Build-time:
We provide a tool which will instrument your source code at build time. This will likely require a small change to your build process, but will require no deployment changes.

Please tell us a bit about what frameworks, drivers, and systems you integrate with. This will help us prioritise which things we provide instrumentation for.

Elastic APM intends to gather some process and Go-specific metrics, e.g. heap usage, garbage collection stats, number of running goroutines. As well as this, we would like to make it easy for you to export application-specific metrics to the Elastic Stack, to view alongside your base APM and logging data.

(Phew!)