False positive for SYSLIB1006 when user haven't specified EventID

[maxkoshevoi]

Description

Related to discussion in #70147 (reply in thread)
CC: @davidfowl

SYSLIB1006 warning states that multiple logging methods cannot use the same event ID.

But it also fires when EventID isn't specified at all. I've annotated my methods without event id:

[LoggerMessage(Level = LogLevel.Information, Message = "Hi there")]
...
[LoggerMessage(Level = LogLevel.Information, Message = "Hi there2")]

and still get a SYSLIB1006 warning.

Reproduction Steps

Shown above

Expected behavior

No warning or at least lower severity event

Actual behavior

Warning which fails the build (since we have Treat warnings as errors enabled)

Regression?

No

Known Workarounds

Disable the warning

Configuration

No response

Other information

No response

[ghost]

Tagging subscribers to this area: @dotnet/area-extensions-logging
See info in area-owners.md if you want to be subscribed.

Issue Details

---

Description

Related to discussion in #70147 (reply in thread)
CC: @davidfowl

SYSLIB1006 warning states that multiple logging methods cannot use the same event ID.

But it also fires when EventID isn't specified at all. I've annotated my methods without event id:

[LoggerMessage(Level = LogLevel.Information, Message = "Hi there")]
...
[LoggerMessage(Level = LogLevel.Information, Message = "Hi there2")]

and still get a SYSLIB1006 warning.

Reproduction Steps

Shown above

Expected behavior

No warning or at least lower severity event

Actual behavior

Warning which fails the build (since we have Treat warnings as errors enabled)

Regression?

No

Known Workarounds

Disable the warning

Configuration

No response

Other information

No response

Author:	maxkoshevoi
Assignees:	-
Labels:	untriaged, area-Extensions-Logging
Milestone:	-

[havocbcn]

According to https://docs.microsoft.com/en-us/dotnet/core/extensions/logging?tabs=command-line#log-event-id
the same EventId could be repeated in different logs.

[davidfowl]

Event ids are per category

[ShreyasJejurkar]

When this would get addressed? I just now hit this issue!