-
Notifications
You must be signed in to change notification settings - Fork 100
instrumentation: Add initial APM tracing #898
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
instrumentation: Add initial APM tracing #898
Conversation
Adds support to enable instrumentation via the APM Go agent. New config options have been added to the `Server` input which could be set up in the `fleet-server` integration configuration. The added instrumentation covers the `fleet-server` http server and the `go-elasticsearch` client. Signed-off-by: Marc Lopez Rubio <[email protected]>
|
This pull request does not have a backport label. Could you fix it @marclop? 🙏
NOTE: |
Signed-off-by: Marc Lopez Rubio <[email protected]>
…-instrumentation-to-server
Signed-off-by: Marc Lopez Rubio <[email protected]>
|
This seems like the right level of integration. |
aleksmaus
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Signed-off-by: Marc Lopez Rubio <[email protected]>
Signed-off-by: Marc Lopez Rubio <[email protected]>
axw
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good!
Signed-off-by: Marc Lopez Rubio <[email protected]>
Signed-off-by: Marc Lopez Rubio <[email protected]>
aleksmaus
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Adds support to enable instrumentation via the APM Go agent. New config
options have been added to the `Server` input which could be set up in
the `fleet-server` integration configuration.
The added instrumentation covers the `fleet-server` http server and the
Adds support to enable instrumentation via the APM Go agent. New config
options have been added to the `Server` input which could be set up in
the `fleet-server` integration configuration.
The added instrumentation covers the `fleet-server` http server and the
`go-elasticsearch` client.
A sample of the configuration that's been added (`instrumentation`):
```yaml
inputs:
- type: fleet-server
server:
instrumentation:
enabled: true
hosts: ["localhost:8200"]
environment: production
secret_token: token
api_key: apikey
```
Signed-off-by: Marc Lopez Rubio <[email protected]>
(cherry picked from commit ade74c7)
Adds support to enable instrumentation via the APM Go agent. New config
options have been added to the `Server` input which could be set up in
the `fleet-server` integration configuration.
The added instrumentation covers the `fleet-server` http server and the
Adds support to enable instrumentation via the APM Go agent. New config
options have been added to the `Server` input which could be set up in
the `fleet-server` integration configuration.
The added instrumentation covers the `fleet-server` http server and the
`go-elasticsearch` client.
A sample of the configuration that's been added (`instrumentation`):
```yaml
inputs:
- type: fleet-server
server:
instrumentation:
enabled: true
hosts: ["localhost:8200"]
environment: production
secret_token: token
api_key: apikey
```
Signed-off-by: Marc Lopez Rubio <[email protected]>
(cherry picked from commit ade74c7)
Co-authored-by: Marc Lopez Rubio <[email protected]>
heavily, heavily influenced by elastic/fleet-server#898
What is the problem this PR solves?
Adds support to enable instrumentation via the APM Go agent. New config
options have been added to the
Serverinput which could be set up inthe
fleet-serverintegration configuration.The added instrumentation covers the
fleet-serverhttp server and thego-elasticsearchclient.A sample of the configuration that's been added (
instrumentation):How does this PR solve the problem?
By using the
go.elastic.co/apmclient.How to test this PR locally
elastic-agentand patch it with a locally built version offleet-server.elasticsearchshows up as a dependency in the APM Service mapChecklist
- [ ] I have made corresponding changes to the documentation- [ ] I have added an entry inCHANGELOG.next.asciidocorCHANGELOG-developer.next.asciidoc.Related issues
Closes #850