Sending huge amount of custom logs to Azure Monitor via Data Collector API causes duplicates

Open
#107 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
20/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
azure
Domain
cloud, observability-sre

Research direction

The issue names no repository files or tests; it describes a published Function App sending about 100,000 rows through Azure Monitor's Data Collector API and receiving duplicates. Start by comparing local and published executions and checking whether submissions are retried or repeated. Done would require identifying and documenting the cause, but the issue does not define a repository change.

Written by the indexing model from the issue text.

Description

I have a function app which collects custom logs from one source and sends them to Azure Monitor using the following code example. The function app runs each hour and sends about 100k rows of log.

Whenever I test the function app locally, it sends the exact amount of log rows, for example 100,000, but when I publish my function app, for some reason it shows in Azure that the number of rows received is slightly more than the original (e.g. 100,050).

What could be the possible reason?

Dominant language
PowerShell
Stars
1.2k
Forks
493
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from microsoft/AzureMonitorCommunity

All issues in microsoft/AzureMonitorCommunity

Similar issues

More Cloud issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.