Consider changing the AzMonitor tests to use OTel instead of Azure.Monitor.Ingestion
Open
@regexrowboat is already working on this.
Since Sep 3, 2025.
server-Azure.Mcp
tools-Monitor
- Dominant language
- C#
- Stars
- 3.7k
- Forks
- 624
- Avg merge
- 2d 20h
- Merged PRs (30d)
- 220
Description
We went with the Ingestion APIs because we need a custom table, which the Logger/Otel approach doesn't seem to support. Since this is working as-is and the suggestion is an improvement, I'm going to create this issue and get this fix in.
>>
just keep using ILogger and just enable otel - it'll forward all ilogger to AzMon, no need for low-level Azure.Monitor.Ingestion
_Originally posted by @lmolkova in https://github.com/Azure/azure-mcp/pull/280#discussion_r2122222026_
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.