Add support for describing the application framework #69
Labels
enhancement
New feature or request
Comments
axw
added a commit
to axw/apm-agent-go
that referenced
this issue
May 4, 2018
Stop exposing the full service model in the tracer - expose only the service name, version, and environment instead. It is now no longer possible to override the agent, language or runtime; and it is no longer possible to set the framework at all. Framework is problematic because it doesn't necessarily apply to all transactions, and there's no way to attach the information at the transaction level. So instead of including it in a problematic state, we'll drop support initially and work updates into the API and server, and then reintroduce it later. See elastic#69
This was referenced Oct 2, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm currently removing the ability for specifying the framework in transaction payloads, because Go's web frameworks tend to be less exclusive of each other. i.e. you could have two web frameworks in the same application. When we can attach the framework info to the transaction, then we'll reinstate support.
This requires changes to the API and API server.
The text was updated successfully, but these errors were encountered: