Golang Agent Local Development Import Statements

Elastic Observability APM
1

Hi there, I am trying to add a new database instrumentation support in golfing agent locally. But I see that by default if I add a new module in place, the import module should point to "go.elastic.co" for me to pull it in my test project.. e.g. in apmmongo the import statement here is go.elastic.co/apm.

How to do local development using the golang agent, when all the import statements are pointing to go.elastic.co/apm?

2

Welcome to the forum @jaamish!

I'm having trouble understanding your question. Can you please explain what have you tried, and what is the issue you have encountered?

3

This topic was automatically closed 20 days after the last reply. New replies are no longer allowed.