This one is with the red "error" icon to it, "Kernel-EventTracing" ID 1:

"Session "PerfDiag Logger" failed to start with the following error: 0xC0000035"

Log Name: Microsoft-Windows-Kernel-EventTracing/Admin
Source: Microsoft-Windows-Kernel-EventTracing
Date: 11/6/2020 3:37:27 AM
Event ID: 2
Task Category: Session
Level: Error
Keywords: Session
User: SYSTEM
Computer: DESKTOP-BIIKR33
Description:
Session "PerfDiag Logger" failed to start with the following error: 0xC0000035
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Kernel-EventTracing" Guid="{b675ec37-bdb6-4648-bc92-f3fdc74d3ca2}" />
<EventID>2</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>2</Task>
<Opcode>12</Opcode>
<Keywords>0x8000000000000010</Keywords>
<TimeCreated SystemTime="2020-11-06T11:37:27.8687665Z" />
<EventRecordID>67</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="256" />
<Channel>Microsoft-Windows-Kernel-EventTracing/Admin</Channel>
<Computer>DESKTOP-BIIKR33</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="SessionName">PerfDiag Logger</Data>
<Data Name="FileName">
</Data>
<Data Name="ErrorCode">3221225525</Data>
<Data Name="LoggingMode">8388736</Data>
</EventData>
</Event>

Then right next to it is the warning yellow icon which is "Kernel-EventTracing" ID 2:

"The backing-file for the real-time session "DefenderApiLogger" has reached its maximum size. As a result, new events will not be logged to this session until space becomes available. This error is often caused by starting a trace session in real-time mode without having any real-time consumers."

Log Name: Microsoft-Windows-Kernel-EventTracing/Admin
Source: Microsoft-Windows-Kernel-EventTracing
Date: 11/6/2020 1:20:05 PM
Event ID: 1
Task Category: Logging
Level: Warning
Keywords: Session
User: SYSTEM
Computer: DESKTOP-BIIKR33
Description:
The backing-file for the real-time session "DefenderApiLogger" has reached its maximum size. As a result, new events will not be logged to this session until space becomes available. This error is often caused by starting a trace session in real-time mode without having any real-time consumers.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Kernel-EventTracing" Guid="{b675ec37-bdb6-4648-bc92-f3fdc74d3ca2}" />
<EventID>1</EventID>
<Version>0</Version>
<Level>3</Level>
<Task>1</Task>
<Opcode>10</Opcode>
<Keywords>0x8000000000000010</Keywords>
<TimeCreated SystemTime="2020-11-06T21:20:05.2754601Z" />
<EventRecordID>68</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="176" />
<Channel>Microsoft-Windows-Kernel-EventTracing/Admin</Channel>
<Computer>DESKTOP-BIIKR33</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="SessionName">DefenderApiLogger</Data>
<Data Name="ErrorCode">3221225864</Data>
<Data Name="LoggingMode">411042176</Data>
</EventData>
</Event>

Both are related correct? from the warning report i need to set DefenderApiLogger to "file-real-time" or boost the size in order to stop the other "error"?