-
Notifications
You must be signed in to change notification settings - Fork 169
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
[REQUEST]: APM agent direct logs #2362
Comments
As there are multiple ways to send logs now (Filebeat, Elastic Agent, APM Agents), we should give an overview of the options, their tradeoffs, and provide guidance on when to use which option. Also, in it's current form, the APM Agents option has a few caveats that should be documented. For example, custom fields aren't supported and a high rate in logs may result in transactions and metrics to be dropped. |
Step one complete in #2452. A list of follow-up updates is in the description. |
@bmorelli25 the support for direct logs sending has been merged for Java APM agent (thus about to be released soon). Is there anything I could contribute here to move this forward ? |
Thanks for the nudge, @SylvainJuge :) I've opened #2542 and elastic/ecs-logging#72 to address the follow-ups. The only thing left is to update links to the Java agent docs after they are live. I didn't have time today to open a draft PR for that, but I will tomorrow. |
I think we should also link to the Java agent docs for directly sending logs from the ecs-logging-java docs |
Everything is done except for links to the Java agent docs from the logs guide and the ECS logging book. Please leave a comment here when direct logs has been released, and I'll publish those last two links. |
@bmorelli25 the Java agent 1.36.0 was just released a few minutes ago, thus log sending is now official. |
All done 🚢 |
Description
Document APM agents sending logs directly to APM Server.
Resources
Collaboration
TBD. The docs and product team will work together to determine the best path forward.
Point of contact.
Main contact: @SylvainJuge
Stakeholders: @felixbarny
The text was updated successfully, but these errors were encountered: