Skip to content

Conversation

@xrmx
Copy link
Member

@xrmx xrmx commented Dec 5, 2024

What does this pull request do?

Document some of the differences between the APM Python agent and EDOT.

Related issues

Closes #123

@xrmx xrmx requested a review from estolfo December 5, 2024 11:24
@xrmx
Copy link
Member Author

xrmx commented Dec 9, 2024

@akhileshpok Would appreciate a review of this from your point of view. Maybe we are overpromising :)

Copy link
Contributor

@colleenmcginnis colleenmcginnis left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I left some suggestions below. Feel free to take them or leave them as you see fit!


### Missing instrumentations

Not all instrumentations we have in Elastic APM Python Agent have an OpenTelemetry counterpart. But we may port them if they are requested by users.
Copy link
Contributor

@colleenmcginnis colleenmcginnis Dec 10, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we be more specific about how to request additional instrumentations? Maybe opening an issue using the feature request template?

Suggested change
Not all instrumentations we have in Elastic APM Python Agent have an OpenTelemetry counterpart. But we may port them if they are requested by users.
Not all instrumentations we have in the Elastic APM Python agent have an OpenTelemetry counterpart. If you would like to see a specific instrumentation ported to OpenTelemetry, submit a [feature request](https://github.com/elastic/elastic-otel-python/issues/new?template=Feature_request.md).

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would prefer to get these from support / product people instead of github users though 😅

xrmx and others added 7 commits December 11, 2024 12:05
Co-authored-by: Colleen McGinnis <[email protected]>
Co-authored-by: Colleen McGinnis <[email protected]>
Co-authored-by: Colleen McGinnis <[email protected]>
Co-authored-by: Colleen McGinnis <[email protected]>
Co-authored-by: Colleen McGinnis <[email protected]>
Co-authored-by: Colleen McGinnis <[email protected]>
Co-authored-by: Colleen McGinnis <[email protected]>
Copy link

@akhileshpok akhileshpok left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Are there any other features that are only supported in the classic Python Agent, e.g., compressed spans? We should list any feature that is only supported in the classic Python Agent in this doc as well. Thanks

@xrmx
Copy link
Member Author

xrmx commented Jan 17, 2025

Are there any other features that are only supported in the classic Python Agent, e.g., compressed spans? We should list any feature that is only supported in the classic Python Agent in this doc as well. Thanks

Updated the document with missing integration with structured logging, span compression and breakdown metrics.

@xrmx xrmx requested review from estolfo and hegerchr January 17, 2025 14:55
Copy link

@hegerchr hegerchr left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @xrmx,
I left some comments based on question I had while reading the document. What do you think?


## Bold on autoinstrumentation

We have chosen to make autoinstrumentation as simple as possible so you can just focus on your code; we favored an experience that requires minimal changes to your application code. The upstream OpenTelemetry configuration has more options than the distribution requires.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What if the reader wants to know how to make use of the upstream configuration of what we consider not required? Do we want to add some instructions or a link to a page with instructions here?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We list our configuration in the README (https://github.com/elastic/elastic-otel-python?tab=readme-ov-file#configuration), I can link it here.

@xrmx xrmx requested a review from hegerchr February 5, 2025 17:15
@xrmx xrmx merged commit 065d4c6 into main Feb 6, 2025
11 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

migration plan and guide from classic agent

5 participants