-
Notifications
You must be signed in to change notification settings - Fork 197
Updating EDOT collector configuration samples for mOTLP input #10569
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
base: main
Are you sure you want to change the base?
Conversation
Signed-off-by: Andreas Gkizas <[email protected]>
This pull request does not have a backport label. Could you fix it @gizas? 🙏
|
Signed-off-by: Andreas Gkizas <[email protected]>
@vigneshshanmugam @gizas This should bear backport labels to all versions where it applies (or at least all the active ones). |
Thanks @theletterf . I added backport-active-9. I think those are the ones for Motel. Please correct me on this |
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.
Approved. We'll also need @vigneshshanmugam approval before going ahead.
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.
These are just samples configuration.
This is the default configuration used by EDOT ->mOTLP -
elastic-agent/deploy/helm/edot-collector/kube-stack/managed_otlp/values.yaml
Lines 558 to 562 in a3f71c4
otlp/ingest: | |
endpoint: ${env:ELASTIC_OTLP_ENDPOINT} | |
headers: | |
Authorization: ApiKey ${env:ELASTIC_API_KEY} | |
timeout: 15s |
Co-authored-by: Vignesh Shanmugam <[email protected]>
Signed-off-by: Andreas Gkizas <[email protected]>
Thank you Vignesh. See updating kube-stack values |
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.
I think we should apply the same changes to the "Logs essential Onboarding" configuration as well:
elastic-agent/deploy/helm/edot-collector/kube-stack/managed_otlp/logs-values.yaml
Line 243 in 808acef
otlp/ingest: |
Signed-off-by: Andreas Gkizas <[email protected]>
Roger thanks, done updating logs-values |
@rogercoll https://buildkite.com/elastic/elastic-agent/builds/28874#0199ed58-74d0-4784-8fca-7d9b48c71892 is not happy due to |
Looks like the |
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.
Need to remove batch processor settings.
Signed-off-by: Andreas Gkizas <[email protected]>
Signed-off-by: Andreas Gkizas <[email protected]>
Signed-off-by: Andreas Gkizas <[email protected]>
Signed-off-by: Andreas Gkizas <[email protected]>
💚 Build Succeeded
History
cc @gizas |
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
kind: other | ||
|
||
# Change summary; a 80ish characters long description of the change. | ||
summary: Updating EDOT gateway collector configuration samples for mOTLP input |
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.
summary: Updating EDOT gateway collector configuration samples for mOTLP input | |
summary: Updating EDOT gateway collector batch configuration when ingesting to mOTLP endpoint. |
send_batch_max_size: 1500 | ||
batch/metrics: | ||
# explicitly set send_batch_max_size to 0, as splitting metrics requests may cause version_conflict_engine_exception in TSDB | ||
send_batch_max_size: 0 |
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.
@carsonip Please check this once value once since we moved off from processor -> exporter batch and wanted to make sure we are not regressing with this.
What does this PR do?
Updates the Managed OTLP Configuration samples with sending queue configuration. The sending queue and batching configuration has been analysed and calculated and we provide here the final suggestions.
Why is it important?
In order to suggest the optimal configuration to our users with batching enabled