search

netdata / msi-installer

Netdata installer for Windows using WSL2
GNU General Public License v3.0
21 stars 2 forks source link

When using, only the traffic of the WSL network card is detected, but the traffic of the network card that my system is really using is not detected #29

Closed KNaiFen closed 1 year ago

KNaiFen commented 1 year ago

When using, only the traffic of the WSL network card is detected, but the traffic of the network card that my system is really using is not detected When using Docker on Win2022, it is the same as the current situation. Only the traffic generated by the WSL network card can be monitored. Is there any solution?Let me monitor the real network card traffic In addition, I noticed that the window was refreshed quickly during installation. I noticed that the red ink was reported, but the window did not give me any time to respond. After the fast refresh, the window closed itself, causing me to see no error messages

cakrit commented 1 year ago

The installation is messed up now, and you see irrelevant things. See if you have the same as shown below. If you do, move netdata.conf? to netdata.conf and run restart-netdata on a cmd shell.

@dfpr see below, something is broken now.

image
cakrit commented 1 year ago

@KNaiFen your data should still appear as seen below, but we know how confusing all the other charts are, which is why netdata.conf should have been customized to disable those collectors by default.

image
KNaiFen commented 1 year ago

I'm sorry that my ”restart-netdata“ doesn't work. I forgot to explain this before. I'm sorry 3

dfpr commented 1 year ago

@KNaiFen you can find the installation log at c:\netdata.log, latest commit also removes red text from installation script and adds more logging to the path adjustment, try it please since I have not been able to reproduce your 'restart-netdata' script issue.

@cakrit netdata.conf issue was caused by incorrect script encoding, it should work correctly now with the latest commit

cakrit commented 1 year ago

@dfpr sorry but I still see the exact same result. I even triggered the build again, in case it wasn't done after the commit you mentioned.

dfpr commented 1 year ago

@dfpr sorry but I still see the exact same result. I even triggered the build again, in case it wasn't done after the commit you mentioned.

fixed, build action was checking out using Windows line endings for linux scripts btw, commits don't automatically trigger the Build action currently

cakrit commented 1 year ago

Yes, @Ferroin will automate that eventually, but for now we need to trigger builds manually.

cakrit commented 1 year ago

The proper default config is back in and works fine.