Skip to content
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

feat: Support OpenTelemetry Azure monitor distro #1509

Merged
merged 25 commits into from
Aug 8, 2024
Merged

Conversation

lzchen
Copy link
Member

@lzchen lzchen commented Jun 11, 2024

Description

We are planning to support auto instrumentation of Azure monitor distro for azure functions. This allows automatic collection of telemetry using OpenTelemetry apis/sdks in users applications in azure functions. The current design is an opt-in model which is controlled by an Appsetting PYTHON_ENABLE_OPENTELEMETRY. The worker takes an indirect dependency on the distro package and attempts to load/instrument with it via configure_azure_monitor() api provided. The idea is to have this package already preinstalled into the functions image. Until the images are pushed out with this package, you may test this change by manually installing the distro onto your dev environment.

Additionally, any exceptions thrown by the distro are caught and logged accordingly. A telemetry sdk should never cause a user's application to crash.

@gavin-aguiar @vrdmr

@lzchen
Copy link
Member Author

lzchen commented Jun 11, 2024

@gavin-aguiar

Since this is a telemetry sdk meant only to be loaded once, I have placed this in worker_init_request. Is there anything special that happens during environment_reload_request that needs to be done pertaining this in your opinion?

@gavin-aguiar
Copy link
Contributor

/azp run

Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@gavin-aguiar
Copy link
Contributor

/azp run

Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@lzchen
Copy link
Member Author

lzchen commented Jul 3, 2024

/azp run

Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@lzchen
Copy link
Member Author

lzchen commented Jul 3, 2024

/azp run

Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@lzchen
Copy link
Member Author

lzchen commented Jul 3, 2024

/azp run

Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@lzchen
Copy link
Member Author

lzchen commented Aug 1, 2024

/azp run

Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@lzchen
Copy link
Member Author

lzchen commented Aug 1, 2024

/azp run

Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@Azure Azure deleted a comment from gavin-aguiar Aug 2, 2024
@gavin-aguiar
Copy link
Contributor

/azp run

Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@lzchen
Copy link
Member Author

lzchen commented Aug 6, 2024

/azp run

Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@gavin-aguiar
Copy link
Contributor

/azp run

Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@gavin-aguiar gavin-aguiar merged commit d5c02fb into Azure:dev Aug 8, 2024
12 checks passed
@lzchen lzchen deleted the ot branch August 8, 2024 23:19
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.

3 participants