Skip to content

Comments

Add Azure Monitor receiver to EDOT Collector#12919

Open
zmoog wants to merge 1 commit intomainfrom
add-azuremonitorreceiver-to-edot
Open

Add Azure Monitor receiver to EDOT Collector#12919
zmoog wants to merge 1 commit intomainfrom
add-azuremonitorreceiver-to-edot

Conversation

@zmoog
Copy link

@zmoog zmoog commented Feb 23, 2026

What does this PR do?

Adds the azuremonitorreceiver from the OTel Collector Contrib repository to the EDOT Collector.

Why is it important?

The Azure Monitor receiver would provide metrics scraping to fill the gaps in namespaces not supported by streaming via Diagnostic Settings / Data Collection Rules (DS/DCR).

Checklist

  • I have read and understood the pull request guidelines of this project.
  • My code follows the style guidelines of this project
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • I have made corresponding change to the default configuration files
  • I have added tests that prove my fix is effective or that my feature works
  • I have added an entry in ./changelog/fragments using the changelog tool
  • I have added an integration test or an E2E test

Related issues

  • n/a

Made with Cursor

Co-authored-by: Cursor <cursoragent@cursor.com>
@zmoog zmoog requested review from a team as code owners February 23, 2026 22:06
@mergify
Copy link
Contributor

mergify bot commented Feb 23, 2026

This pull request does not have a backport label. Could you fix it @zmoog? 🙏
To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

  • backport-./d./d is the label that automatically backports to the 8./d branch. /d is the digit
  • backport-active-all is the label that automatically backports to all active branches.
  • backport-active-8 is the label that automatically backports to all active minor branches for the 8 major.
  • backport-active-9 is the label that automatically backports to all active minor branches for the 9 major.

@github-actions
Copy link
Contributor

@github-actions
Copy link
Contributor

✅ Vale Linting Results

No issues found on modified lines!


The Vale linter checks documentation changes against the Elastic Docs style guide.

To use Vale locally or report issues, refer to Elastic style guide for Vale.

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