Ether Wrangler

I don't think there is a way to change the editor globally because each container will have it's own configuration. I also don't see any way in the web console to verify if the alert is configured or not, but based on the second post, you are at least getting Discord alerts for some of the built in alerts. As to what that alert means, I've never seen that, but I have a static IP Address on my server. If no one else chimes in here with an idea, you might want to take that message to the General Support forum since I think whatever is causing that is going to be from UnRAID itself and not this docker.

That's vi. Here's a link on how to use it: https://www.howtogeek.com/102468/a-beginners-guide-to-editing-text-files-with-vi/. If you'd rather use nano (at least learn the vi exit sequence though) then run: apt update && apt install nano select-editor When you run select-editor you should get an option to change from vim-tiny to nano. My only guess is that I installed nano in the past and set it as the default edit and forgot about it.

Sorry, been a busy week at work. If you don't change the file permissions then Krusader probably won't have the correct ones to save the file. Not sure what those 3 you have highlighted are, but it does look like the correct file got created (circled in red) If the text editor in your terminal looks like this at the bottom: That's an editor called "nano" if you ever want to watch a video to learn more about it. All of those are the cheat codes for the common shortcuts and ^ is the "modifier key". The default modifier in nano is ctrl. So to save and exit you can do ctrl-o (Write Out) then ctrl-x (Exit). Or you can just do ctrl-x and it will ask if you want to save the buffer and you can answer y/n.

If you have the latest version of the template (updated at the end of October) you'll have all you need in the template for Cloud. To see where the container is creating the AppData, click "Show more settings" at the bottom of the netdata docker settings page. In there you'll see three paths: NetData_Config, NetData_Lib, and NetData_Cache. Make sure all 3 of those are mapped or you'll have issues with NetData Cloud persisting data and setting up the config for Alerts. Go to https://www.netdata.cloud/ and sign up for an account. You'll get to the point you'll be given instructions to install netdata on something and those instructions should have a Claim Token, Claim URL, and a Claim Room. You'll paste all 3 of those into the 3 fields into the template and Unraid should start showing up in Netdata Cloud. To setup the Discord portion, this should walk you through it: https://learn.netdata.cloud/docs/alerting/notifications/agent-dispatched-notifications/discord When you get to: sudo ./edit-config health_alarm_notify.conf Ignore the sudo command. If you do the Test Notification section, I don't think you'll do the following: # become user netdata sudo su -s /bin/bash netdata To change the ram alert settings, run this command after you are done editing the config above: ./edit-config health.d/ram.conf In there you can change the settings to however you would like. For more info on that one, here's the documentation on setting those up: https://learn.netdata.cloud/docs/alerting/health-configuration-reference

I do not see anything like this in the syslog on Unraid or in the docker log for Netdata on my system. Which log file do you have these in?

The sudo command isn't working because that package is not in the image. Also on my install I have not been able to find the netdata_random_session_id file. I don't see this file in a quick google search either. Can you post a link on what you are trying to do? For the second part, it looks like you have to change the alert settings via CLI. You'll have to edit two files from inside off the netdata container's cli (one to change the alert's config, another to actually give netdata the settings to send the Discord notifications). You'll also have to create a new webhook/bot in discord that will be used in that second file. Let me know if this is something you want to look at and I can try to help you, but I saw in your other thread that you think you have the issue narrowed down to Plex.

Also, the Time Zone variable is being defined wrong. You could probably remove this entirely as Unraid has started passing a TZ variable through natively at some point.

A change request was merged in two days ago adding all of the missing mounts as well as the needed cloud claim tokens.

The template has that taken care of with an argument in Extra Parameters. This template is ready to go if you want NetData locally. If you want NetData Cloud to work properly, you'll need to add the variables and path mappings from these two posts I made.

If you mean having to add it back to the cloud every time, check my post above yours. That shows the additional mappings to add to keep that from happening. I'm working on submitting a pull request to roland to update this template with those values.

I think I finally got this fixed. I'm still not sure why I was getting the traces with no macvlan docker networks, but I saw the comment about disabling bridging as its not needed anymore with the macvtap device that will be created. I turned off bridging on the NIC and have made it 2 days with no traces. Before this I was getting multiple every day with hard locks of the OS at least every 2 days.

One other thing I noticed after a couple of reboots is that if you don't persist some of the directories in this docker, it will show up as a new device in NetData Cloud. I added these mappings to fix that and get the OS to show correctly (Slackware) and to fix group/user enumeration.

I'm still getting what appear to be macvlan call traces after applying this. The odd thing is, I set the network type to ipvlan in 6.12.3 and if I check the docker networks there isn't even a macvlan network. NETWORK ID NAME DRIVER SCOPE 68ad20afc8e2 bridge bridge local a7904065acfc host host local 85c9f1a91a4e none null local a66a6a6c0090 proxynet bridge local tower-diagnostics-20230908-1718.zip

If any of you are still looking to set this up to work with NetData Cloud: Login to your cloud account and under Integrations > Deploy > Docker & Kubernetes > click Docker Copy the Docker CLI output and paste it into Notepad or a text editor Back in Unraid either edit the settings on your existing NetData docker or add one Click "Add another Path, Port, Variable, Label or Device" Change the type to Variable For Name and Key paste in NETDATA_CLAIM_TOKEN For Value paste in your claim token from your text file Repeat adding variables and values for NETDATA_CLAIM_URL and NETDATA_CLAIM_ROOMS