Forum Discussion

am1357's avatar
am1357
Brass Contributor
Jul 17, 2023
Solved

MDI NetworkActivityEntityResolver Log Warnings

Hi,


I am seeing a lot of NetworkActivityEntityResolver warnings in the Microsoft.Tri.Sensor.log on one DC.

There are no open sensor integration/health alerts in the M365D portal.

 

Here's what the logs look like. This warning with different computer object IDs is being generated every second:

 

NetworkActivityEntityResolver ResolveNetlogonAsync Parsed OperationType=NetrLogonSamLogonEx PayloadLength=800 SourceComputerId=XXXXXX

 

Where would I start to troubleshoot this issue?

 

Thanks

  • This is normal.
    The logs are configured to keep latest total of 10 files, 50MB each. so it is capped.
    No danger of reaching 0 disk space assuming initial space is aligned with requirements in the docs.

3 Replies

  • Nothing to be alarmed about.
    Those logs are not designed to be a tool for customers, it's mainly for MDI support and PG engineers.
    The fact that some traces are at Warn level does not mean something wrong has happened,
    we just use it to differentiate importance of the log to us compared to Debug or Info levels.
    If you see lots of errors and exceptions, or portal health alerts, then it increases the chances of something being really wrong,
    which can also give the warn messages a new significance, but that requires "internal" knowledge on how the system works, so I would only let Support & PG to give meaning to these logs.

    • am1357's avatar
      am1357
      Brass Contributor
      Thanks, Eli. Good to know that these warnings don't have an impact on the functionality of MDI.
      I was only concerned as these warnings generate multiple 50MB archived log files in the logs folder of MDI.
      • EliOfek's avatar
        EliOfek
        Icon for Microsoft rankMicrosoft
        This is normal.
        The logs are configured to keep latest total of 10 files, 50MB each. so it is capped.
        No danger of reaching 0 disk space assuming initial space is aligned with requirements in the docs.

Resources