-
Notifications
You must be signed in to change notification settings - Fork 429
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
[Golang] Add Integration Package with expvar Data Stream #4933
Conversation
/test |
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!
🌐 Coverage report
|
- name: golang | ||
type: group | ||
fields: | ||
- name: expvar |
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.
There are many more fields in the beats sample module https://www.elastic.co/guide/en/beats/metricbeat/current/metricbeat-metricset-golang-expvar.html
Are we dropping out some fields for expvar ?
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.
Not actually, We looked into those additional fields but those fields aren’t default golang metric fields, for example, beat.cpu.system.ticks is a field of system system.cpu.system.ticks, we ran go module and its not collecting these fields, go has the functionality to expose custom metrics and these could be custom metrics for which we are providing support. If the user has these or any other custom fields exposed in their application, these will be automatically inserted in our document.
@@ -0,0 +1,40 @@ | |||
title: Golang expvar metrics | |||
type: logs |
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.
Wondering if there a simpler way to re-direct these metrics from filebeat httpjson to metrics-* data-stream or metrics-* data view. Explore, if it is feasible.
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.
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.
elastic/elastic-agent#2208: This is the agent issue opened to track the same
{{/if}} | ||
{{/if}} | ||
processors: | ||
- add_fields: |
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.
Why is this processor added here and not as part of ingest pipeline ?
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.
We need service.address to differentiate data among different hosts if the user has added multiple integrations. We can not add this processor in pipeline since we require accessing the input parameter(hostname) here which can not be done from pipeline.
As we have planned to skip some of the gc_pause fields for now. |
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!
Please take care of opening an issue as shared in this comment.
As part of this datastream, We don't need to drop any fields. There are some fields in Heap datastream that will be dropped. We'll address them as part of heap PR. |
Package golang - 0.2.0 containing this change is available at https://epr.elastic.co/search?package=golang |
What does this PR do?
Checklist
changelog.yml
file.How to test this PR locally
Related issues
Screenshots