Just installed it on a 6.6.7 install, and it's looking good. However, I'm getting an alert in it about my cache drive, saying that the btrfs allocation is 97.3%. However, if I look at my unraid dashboard, it's only around 60% allocated (157GB out of 256GB).

Any clue why this alert is being raised, and how I may clear it?

 

Edited May 11, 20197 yr by Caldorian
Attach screenshot

can someone please let me know if there is anything else I need to do other than doing nvidia_smi: yes in python.d.conf to get this to work. 

 

 

An update has broken this again.

Looking into what broke it.

On 5/4/2019 at 1:37 AM, roland said:

Hi, sorry for the long absence.

I think you should be able to add the file into the override folder and it should persist.

I don't have a nvidia and can't test it.

See this section: Adding custom alarms, charts and configuration overrides

on the dockerhub description: https://hub.docker.com/r/titpetric/netdata

Please let me know if you think something else is required.

 

I don't maintain the docker container, just made the template for easy use in unRAID.

 

 

Edit: @Dazog @dbinott

I think the change a while back where the override folder was created did not work properly anymore with my template.

Please change the docker mapping from:

-v '/mnt/cache/appdata/netdata':'/etc/netdata':'rw'

to this and try if this works:

-v '/mnt/cache/appdata/netdata':'/etc/netdata/override':'rw'

it works for me for the normal netdata.conf file.

If you could confirm this works I will change the template to make it easier for the next users.

 

Edit2: 

turns out I made that change in the template more than a year ago ... 

just never changed my own setup. SO if you added netdata recently it should work!

 

regards

  Roland

OK, stupid question... How do I edit the file?? It doesn't seem like nano / vim work in the console. I tried viewing the files via Krusader but the Netdata folder in appdata is empty?

5 hours ago, CowboyRedBeard said:

OK, stupid question... How do I edit the file?? It doesn't seem like nano / vim work in the console. I tried viewing the files via Krusader but the Netdata folder in appdata is empty?

Check out the how to change the configuration topic in the first post. 

Hello-

 

I have been having some issues with Netdata.  The docker log is full of errors and I also get some sock errors in the main log.  Can anyone help me out?  I tried Googling and looking online but some of the things to try make me nervous as they are over my head and I don't want to follow blindly for fear of making it worse.  Here is a pic of the 2 log files:

 

Docker Log:

 

Main Log:

 

Thanks for any help!

-Jason

Every single day when I check for updates, NetData comes up as having an update.  Sometimes 2x a day.  Are updates really being published for this app this frequently?  The last post on this forum was early June...so I'm wondering if I've just been updating over itself over and over this whole time???

Edited August 26, 20196 yr by Boldly_Goes

3 minutes ago, Boldly_Goes said:

Are updates really being published for this app this frequently?

Yup. 

HOW TO TEMPERATURES VOLTAGES FANS

 

- Go to http://unraid:19999/netdata.conf (change unraid for your unraid servername or ip, my case is called unraid)

- Paste the contents in a text editor

- Find the [plugins] section

- Change the line where says # python.d = yes for python.d = yes (so remove the # at the beginning of that line)

- Copy the content of your text editor and paste the content in a new file called netdata.conf in /mnt/user/appdata/netdata (or wherever you have configured the data of your unraid)

- Now copy and paste the content of this: https://raw.githubusercontent.com/netdata/netdata/master/collectors/python.d.plugin/python.d.conf in a text editor

- Find the line # sensors: yes and change it for sensors: yes (remove the # at the beginning of that line)

- Save this file as python.d.conf in /mnt/user/appdata/netdata

- Create a folder python.d in /mnt/user/appdata/netdata

- Copy the contents of https://raw.githubusercontent.com/netdata/netdata/master/collectors/python.d.plugin/sensors/sensors.conf in a text editor

- Check the lines that starts with types:  and add a # at the beginning of each sensor that you DON'T want to have in netdata

- Save this file as sensors.conf in /mnt/user/appdata/netdata/python.d

- Restart the Docker of netdata, and you will see a new section called Sensors and there all your temperatures and voltages and more

 

If after all of this, still not works, I recommend to install Dynamix System Temperature and configure it properly, you should be able to see temperatures in the footer of unraid admin web, as that tool configures the command sensors to work as expected and therefore the plugin for netdata can read those sensors too.

 

Hope this Helps

 

HOW TO CUSTOM DASHBOARDS

 

- Go to your unraid Docker config tab
- Edit NetData Docker
- Click on "Add another Path, Port, Variable, Label or Device"
    - Config Type: path
    - name custom-web
    - Container Path:
    - Host Path:
    - Access Mode: Read/Write
    - Description: Path for custom dashboards
- Restart your netdata docker
- Go to http://unraid:19999/dashboards.html
- Copy the example in a new file dash.html in /mnt/user/appdata/netdata-web-custom
- Go to http://unraid:19999/custom/dash.html
- Check https://docs.netdata.cloud/web/gui/custom/#custom-dashboards for more information

 

Other tips

 

Increase refresh rate of graphs
To increase the refresh rate of the charts, you will need to add data-points="600" to each graph you want to increase its refresh rate, play with the number (600 in this example) to increase / decrease the refresh rate

 

Make the dashboard to update when lost its focus
Add the following script AFTER <script type="text/javascript" src="http://unraid:19999/dashboard.js"></script>

<script type="text/javascript">
    NETDATA.options.current.destroy_on_hide = true;
    NETDATA.options.current.concurrent_refreshes = true;
    NETDATA.options.current.parallel_refresher = true;
    NETDATA.options.current.stop_updates_when_focus_is_lost = false;
    NETDATA.options.current.sync_selection = false;
</script>

 

Paint it Black (dark theme)
Add the following script BEFORE <script type="text/javascript" src="http://unraid:19999/dashboard.js"></script>

<script type="text/javascript">
    var netdataTheme = "slate";
</script>

 

 

EXAMPLE of Dashboard for a 8 Core system:

 

<!DOCTYPE html>
<html lang="en">
  <head>
    <title>Custom unRaid Dashboard</title>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
    <meta charset="utf-8" />
    <meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1" />
    <meta name="viewport" content="width=device-width, initial-scale=1" />
    <meta name="apple-mobile-web-app-capable" content="yes" />
    <meta
      name="apple-mobile-web-app-status-bar-style"
      content="black-translucent"
    />
    <style type="text/css">
      .row {
        display: flex;
        flex-direction: row;
        justify-content: center;
        align-content: center;
      }
      .col {
        display: flex;
        flex-direction: column;
        justify-content: center;
        align-content: center;
      }
      .cell-1-3 {
        width: 33%;
      }
      .cell-1-4 {
        width: 25%;
      }
      .cell-1-5 {
        width: 20%;
      }
      .cell-1-6 {
        width: 16.66%;
      }
      .cell-1-8 {
        width: 12.5%;
      }

      html body {
        overflow-x: hidden;
      }
      html body .my-container {
        padding: 12px;
        /* background-color: #f0f000;
				background-color: #ff9000; */
      }
    </style>
  </head>
  <body>
    <div class="my-container">
      <div class="row">
        <div class="cell-1-6">
          <div
            data-netdata="sensors.k10temp_pci_00c3_temperature"
            data-title="CPU Temperature"
            data-points="600"
            data-chart-library="gauge"
            data-width="100%"
            data-gauge-max-value="85"
            data-gauge-generate-gradient="[0, 75, 80, 93, 100]"
            data-gauge-gradient-percent-color-0="#35a035"
            data-gauge-gradient-percent-color-75="#35a035"
            data-gauge-gradient-percent-color-80="#f0f000"
            data-gauge-gradient-percent-color-93="#ff9000"
            data-gauge-gradient-percent-color-100="#ff2020"
          ></div>
        </div>
        <div class="cell-1-6">
          <div
            data-netdata="system.cpu"
            data-title="CPU Load"
            data-points="600"
            data-chart-library="gauge"
            data-gauge-max-value="100"
            data-width="100%"
            data-gauge-generate-gradient="[0, 75, 80, 93, 100]"
            data-gauge-gradient-percent-color-0="#35a035"
            data-gauge-gradient-percent-color-75="#35a035"
            data-gauge-gradient-percent-color-80="#f0f000"
            data-gauge-gradient-percent-color-93="#ff9000"
            data-gauge-gradient-percent-color-100="#ff2020"
          ></div>
        </div>
        <div class="cell-1-5">
          <div
            data-netdata="sensors.it8720_isa_0228_fan"
            data-title="Pump"
            data-points="600"
            data-dimensions="fan4"
            data-chart-library="gauge"
            data-gauge-max-value="2000"
            data-width="100%"
            data-gauge-generate-gradient="[0, 75, 80, 93, 100]"
            data-gauge-gradient-percent-color-0="#35a035"
            data-gauge-gradient-percent-color-75="#35a035"
            data-gauge-gradient-percent-color-80="#f0f000"
            data-gauge-gradient-percent-color-93="#ff9000"
            data-gauge-gradient-percent-color-100="#ff2020"
          ></div>
        </div>
      </div>
      <div class="row">
        <div class="cell-1-8">
          <div
            data-netdata="cpu.cpufreq"
            data-points="600"
            data-dimensions="cpu0"
            data-title="CPU 0 Frequency"
            data-chart-library="gauge"
            data-gauge-min-value="0"
            data-gauge-max-value="4100"
            data-width="100%"
            data-gauge-start-color="#35a035"
            data-gauge-stop-color="#a03535"
            data-gauge-generate-gradient="[0, 75, 80, 93, 100]"
            data-gauge-gradient-percent-color-0="#35a035"
            data-gauge-gradient-percent-color-75="#35a035"
            data-gauge-gradient-percent-color-80="#f0f000"
            data-gauge-gradient-percent-color-93="#ff9000"
            data-gauge-gradient-percent-color-100="#ff2020"
          ></div>

          <div
            data-netdata="cpu.cpu0"
            data-points="600"
            data-title="CPU 0 Load"
            data-chart-library="gauge"
            data-gauge-max-value="100"
            data-width="100%"
            data-gauge-start-color="#35a035"
            data-gauge-stop-color="#a03535"
            data-gauge-generate-gradient="[0, 75, 80, 93, 100]"
            data-gauge-gradient-percent-color-0="#35a035"
            data-gauge-gradient-percent-color-75="#35a035"
            data-gauge-gradient-percent-color-80="#f0f000"
            data-gauge-gradient-percent-color-93="#ff9000"
            data-gauge-gradient-percent-color-100="#ff2020"
          ></div>
        </div>

        <div class="cell-1-8 col">
          <div
            data-netdata="cpu.cpufreq"
            data-points="600"
            data-dimensions="cpu1"
            data-title="CPU 1 Frequency"
            data-chart-library="gauge"
            data-gauge-max-value="4100"
            data-width="100%"
            data-gauge-start-color="#35a035"
            data-gauge-stop-color="#a03535"
            data-gauge-generate-gradient="[0, 75, 80, 93, 100]"
            data-gauge-gradient-percent-color-0="#35a035"
            data-gauge-gradient-percent-color-75="#35a035"
            data-gauge-gradient-percent-color-80="#f0f000"
            data-gauge-gradient-percent-color-93="#ff9000"
            data-gauge-gradient-percent-color-100="#ff2020"
          ></div>

          <div
            data-netdata="cpu.cpu1"
            data-points="600"
            data-title="CPU 1 Load"
            data-chart-library="gauge"
            data-gauge-max-value="100"
            data-width="100%"
            data-gauge-start-color="#35a035"
            data-gauge-stop-color="#a03535"
            data-gauge-generate-gradient="[0, 75, 80, 93, 100]"
            data-gauge-gradient-percent-color-0="#35a035"
            data-gauge-gradient-percent-color-75="#35a035"
            data-gauge-gradient-percent-color-80="#f0f000"
            data-gauge-gradient-percent-color-93="#ff9000"
            data-gauge-gradient-percent-color-100="#ff2020"
          ></div>
        </div>

        <div class="cell-1-8">
          <div
            data-netdata="cpu.cpufreq"
            data-points="600"
            data-dimensions="cpu2"
            data-title="CPU 2 Frequency"
            data-chart-library="gauge"
            data-gauge-max-value="4100"
            data-width="100%"
            data-gauge-start-color="#35a035"
            data-gauge-stop-color="#a03535"
            data-gauge-generate-gradient="[0, 75, 80, 93, 100]"
            data-gauge-gradient-percent-color-0="#35a035"
            data-gauge-gradient-percent-color-75="#35a035"
            data-gauge-gradient-percent-color-80="#f0f000"
            data-gauge-gradient-percent-color-93="#ff9000"
            data-gauge-gradient-percent-color-100="#ff2020"
          ></div>

          <div
            data-netdata="cpu.cpu2"
            data-points="600"
            data-title="CPU 2 Load"
            data-chart-library="gauge"
            data-gauge-max-value="100"
            data-width="100%"
            data-gauge-start-color="#35a035"
            data-gauge-stop-color="#a03535"
            data-gauge-generate-gradient="[0, 75, 80, 93, 100]"
            data-gauge-gradient-percent-color-0="#35a035"
            data-gauge-gradient-percent-color-75="#35a035"
            data-gauge-gradient-percent-color-80="#f0f000"
            data-gauge-gradient-percent-color-93="#ff9000"
            data-gauge-gradient-percent-color-100="#ff2020"
          ></div>
        </div>

        <div class="cell-1-8">
          <div
            data-netdata="cpu.cpufreq"
            data-points="600"
            data-dimensions="cpu3"
            data-title="CPU 3 Frequency"
            data-chart-library="gauge"
            data-gauge-max-value="4100"
            data-width="100%"
            data-gauge-start-color="#35a035"
            data-gauge-stop-color="#a03535"
            data-gauge-generate-gradient="[0, 75, 80, 93, 100]"
            data-gauge-gradient-percent-color-0="#35a035"
            data-gauge-gradient-percent-color-75="#35a035"
            data-gauge-gradient-percent-color-80="#f0f000"
            data-gauge-gradient-percent-color-93="#ff9000"
            data-gauge-gradient-percent-color-100="#ff2020"
          ></div>

          <div
            data-netdata="cpu.cpu3"
            data-points="600"
            data-title="CPU 3 Load"
            data-chart-library="gauge"
            data-gauge-max-value="100"
            data-width="100%"
            data-gauge-start-color="#35a035"
            data-gauge-stop-color="#a03535"
            data-gauge-generate-gradient="[0, 75, 80, 93, 100]"
            data-gauge-gradient-percent-color-0="#35a035"
            data-gauge-gradient-percent-color-75="#35a035"
            data-gauge-gradient-percent-color-80="#f0f000"
            data-gauge-gradient-percent-color-93="#ff9000"
            data-gauge-gradient-percent-color-100="#ff2020"
          ></div>
        </div>

        <div class="cell-1-8">
          <div
            data-netdata="cpu.cpufreq"
            data-points="600"
            data-dimensions="cpu4"
            data-title="CPU 4 Frequency"
            data-chart-library="gauge"
            data-gauge-max-value="4100"
            data-width="100%"
            data-gauge-start-color="#35a035"
            data-gauge-stop-color="#a03535"
            data-gauge-generate-gradient="[0, 75, 80, 93, 100]"
            data-gauge-gradient-percent-color-0="#35a035"
            data-gauge-gradient-percent-color-75="#35a035"
            data-gauge-gradient-percent-color-80="#f0f000"
            data-gauge-gradient-percent-color-93="#ff9000"
            data-gauge-gradient-percent-color-100="#ff2020"
          ></div>

          <div
            data-netdata="cpu.cpu4"
            data-points="600"
            data-title="CPU 4 Load"
            data-chart-library="gauge"
            data-gauge-max-value="100"
            data-width="100%"
            data-gauge-start-color="#35a035"
            data-gauge-stop-color="#a03535"
            data-gauge-generate-gradient="[0, 75, 80, 93, 100]"
            data-gauge-gradient-percent-color-0="#35a035"
            data-gauge-gradient-percent-color-75="#35a035"
            data-gauge-gradient-percent-color-80="#f0f000"
            data-gauge-gradient-percent-color-93="#ff9000"
            data-gauge-gradient-percent-color-100="#ff2020"
          ></div>
        </div>

        <div class="cell-1-8">
          <div
            data-netdata="cpu.cpufreq"
            data-points="600"
            data-dimensions="cpu5"
            data-title="CPU 5 Frequency"
            data-chart-library="gauge"
            data-gauge-max-value="4100"
            data-width="100%"
            data-gauge-start-color="#35a035"
            data-gauge-stop-color="#a03535"
            data-gauge-generate-gradient="[0, 75, 80, 93, 100]"
            data-gauge-gradient-percent-color-0="#35a035"
            data-gauge-gradient-percent-color-75="#35a035"
            data-gauge-gradient-percent-color-80="#f0f000"
            data-gauge-gradient-percent-color-93="#ff9000"
            data-gauge-gradient-percent-color-100="#ff2020"
          ></div>

          <div
            data-netdata="cpu.cpu5"
            data-points="600"
            data-title="CPU 5 Load"
            data-chart-library="gauge"
            data-gauge-max-value="100"
            data-width="100%"
            data-gauge-generate-gradient="[0, 75, 80, 93, 100]"
            data-gauge-gradient-percent-color-0="#35a035"
            data-gauge-gradient-percent-color-75="#35a035"
            data-gauge-gradient-percent-color-80="#f0f000"
            data-gauge-gradient-percent-color-93="#ff9000"
            data-gauge-gradient-percent-color-100="#ff2020"
          ></div>
        </div>

        <div class="cell-1-8">
          <div
            data-netdata="cpu.cpufreq"
            data-points="600"
            data-dimensions="cpu6"
            data-title="CPU 6 Frequency"
            data-chart-library="gauge"
            data-gauge-max-value="4100"
            data-width="100%"
            data-gauge-generate-gradient="[0, 75, 80, 93, 100]"
            data-gauge-gradient-percent-color-0="#35a035"
            data-gauge-gradient-percent-color-75="#35a035"
            data-gauge-gradient-percent-color-80="#f0f000"
            data-gauge-gradient-percent-color-93="#ff9000"
            data-gauge-gradient-percent-color-100="#ff2020"
          ></div>

          <div
            data-netdata="cpu.cpu6"
            data-points="600"
            data-title="CPU 6 Load"
            data-chart-library="gauge"
            data-gauge-max-value="100"
            data-width="100%"
            data-gauge-generate-gradient="[0, 75, 80, 93, 100]"
            data-gauge-gradient-percent-color-0="#35a035"
            data-gauge-gradient-percent-color-75="#35a035"
            data-gauge-gradient-percent-color-80="#f0f000"
            data-gauge-gradient-percent-color-93="#ff9000"
            data-gauge-gradient-percent-color-100="#ff2020"
          ></div>
        </div>

        <div class="cell-1-8">
          <div
            data-netdata="cpu.cpufreq"
            data-points="600"
            data-dimensions="cpu7"
            data-title="CPU 7 Frequency"
            data-chart-library="gauge"
            data-gauge-max-value="4100"
            data-width="100%"
            data-gauge-generate-gradient="[0, 75, 80, 93, 100]"
            data-gauge-gradient-percent-color-0="#35a035"
            data-gauge-gradient-percent-color-75="#35a035"
            data-gauge-gradient-percent-color-80="#f0f000"
            data-gauge-gradient-percent-color-93="#ff9000"
            data-gauge-gradient-percent-color-100="#ff2020"
          ></div>

          <div
            data-netdata="cpu.cpu7"
            data-points="600"
            data-title="CPU 7 Load"
            data-chart-library="gauge"
            data-gauge-max-value="100"
            data-width="100%"
            data-gauge-generate-gradient="[0, 75, 80, 93, 100]"
            data-gauge-gradient-percent-color-0="#35a035"
            data-gauge-gradient-percent-color-75="#35a035"
            data-gauge-gradient-percent-color-80="#f0f000"
            data-gauge-gradient-percent-color-93="#ff9000"
            data-gauge-gradient-percent-color-100="#ff2020"
          ></div>
        </div>
      </div>

      <div class="row">
        <div
          data-netdata="sensors.k10temp_pci_00c3_temperature"
          data-title="CPU Temperature"
          data-chart-library="dygraph"
          data-dygraph-valuerange="[25,85]"
          data-width="100%"
          data-height="165"
          data-after="-3600"
        ></div>
      </div>

      <div class="row">
        <div
          data-netdata="sensors.it8720_isa_0228_temperature"
          data-title="System Temperatures"
          data-chart-library="dygraph"
          data-dygraph-valuerange="[25,85]"
          data-width="100%"
          data-height="165"
          data-after="-3600"
        ></div>
      </div>
    </div>
    <script type="text/javascript">
      var netdataTheme = "slate";
    </script>
    <script
      type="text/javascript"
      src="http://unraid:19999/dashboard.js"
    ></script>
    <script type="text/javascript">
      NETDATA.options.current.destroy_on_hide = true;
      NETDATA.options.current.concurrent_refreshes = true;
      NETDATA.options.current.parallel_refresher = true;
      NETDATA.options.current.stop_updates_when_focus_is_lost = false;
      NETDATA.options.current.sync_selection = false;
    </script>
  </body>
</html>

Hope this helps!

21 hours ago, danyg said:

HOW TO TEMPERATURES VOLTAGES FANS

 

- Go to http://unraid:19999/netdata.conf (change unraid for your unraid servername or ip, my case is called unraid)

- Paste the contents in a text editor

- Find the [plugins] section

- Change the line where says # python.d = yes for python.d = yes (so remove the # at the beginning of that line)

- Copy the content of your text editor and paste the content in a new file called netdata.conf in /mnt/user/appdata/netdata (or wherever you have configured the data of your unraid)

- Now copy and paste the content of this: https://raw.githubusercontent.com/netdata/netdata/master/collectors/python.d.plugin/python.d.conf in a text editor

- Find the line # sensors: yes and change it for sensors: yes (remove the # at the beginning of that line)

- Save this file as python.d.conf in /mnt/user/appdata/netdata

- Create a folder python.d in /mnt/user/appdata/netdata

- Copy the contents of https://raw.githubusercontent.com/netdata/netdata/master/collectors/python.d.plugin/sensors/sensors.conf in a text editor

- Check the lines that starts with types:  and add a # at the beginning of each sensor that you DON'T want to have in netdata

- Save this file as sensors.conf in /mnt/user/appdata/netdata/python.d

- Restart the Docker of netdata, and you will see a new section called Sensors and there all your temperatures and voltages and more

 

If after all of this, still not works, I recommend to install Dynamix System Temperature and configure it properly, you should be able to see temperatures in the footer of unraid admin web, as that tool configures the command sensors to work as expected and therefore the plugin for netdata can read those sensors too.

 

Hope this Helps

 

First of all, thanks for the tutorial. I've noticed today that the sensors section is gone for me in netdata. It's the first time this happened since I use that docker. That section was there as default since I can remember using this docker, without doin anything special with adding plugins.

 

I followed your tutorial created all the files, with the changes you mentioned and as soon as I start the container the files become empty. Do I have to change something else? Any idea?

CPU temp missing all of a sudden for anyone else?

Edited September 19, 20196 yr by drawde
nevermind, the above solution worked for me

@drawde Same for me. Did you tried what danyg posted above? For me the created files mentioned in the tutorial are emptied as soon as I startup the container and no effect. No stats for fans or temps. 🤨

Hi @bastl @drawde, sorry to hear that, not sure why that is happening to you.
I was checking the official github repo, and the overrides should be loaded as Read Only, but for some reason in the configuration you get from Community Apps comes in Read and Write, so you can try changing it to be Read only.

Also you can try update the docker image, as if you have an old version they might have a bug where they were cleaning that directory at the beginning, I got this kind of recently.

This is just an educated guess as I don't have this problem I restart the docker or even stop it and start it manually and the config is still there.

 

To switch the overrides to read only:

- Edit your netdata docker

- Find the Configuration folder (the one it says Container Path: /etc/netdata/override) and click on override

- In the modal/window that appears locate the option call Access Mode

- Change Access mode to Read Only

- Click Save in the modal/window

- Click Done in the configuration

 

Let me know if that solved your problem

 

 

Edited September 28, 20196 yr by danyg

@danyg I noticed something strange in my docker config. I had 2 paths configured pointed to the same source. The config path (called host path in my old docker) and the override path both pointed to "/mnt/user/appdata/netdata". I guess this caused the issue overriding the files. I completly removed the docker and the config and redownloaded the docker image. Only one path left with the new config and the files i create stay in place. I can't remember ever touch the config before. The container I use for almost 2 years now. Maybe with an update the paths changed and in my config instead of replacing the old declaration the update added a second path.

 

BUT at first I couldn't find any sensor informations after adding your tweaks. After double and triple checking the config files I think I found the issue. A single space in front of the "sensors: yes" in the python.d.conf caused the issue to not showing up the sensor informations in NetData. 😣

 

On 9/16/2019 at 9:16 AM, bastl said:

(remove the # at the beginning of that line)

AND the space between '#' and 'sensors' 😂

Am I using the right docker? Im trying to view the disk and cpu usage of my individual docker containers. I can't find that anywhere.

39 minutes ago, Snipe3000 said:

Am I using the right docker? Im trying to view the disk and cpu usage of my individual docker containers. I can't find that anywhere.

Did you scroll down to where the containers are listed?

6 hours ago, Squid said:

Did you scroll down to where the containers are listed?

I found it, they are invisible until you do the login thing.

Hi!

 

Is there a way to enable the dbengine?

I've got the following error, if I trying to enable it:

"2019-11-02 11:41:07: netdata FATAL : MAIN :RRD_MEMORY_MODE_DBENGINE is not supported in this platform. # : No such file or directory"

On 11/2/2019 at 6:47 AM, Gyurci said:

Hi!

 

Is there a way to enable the dbengine?

I've got the following error, if I trying to enable it:

"2019-11-02 11:41:07: netdata FATAL : MAIN :RRD_MEMORY_MODE_DBENGINE is not supported in this platform. # : No such file or directory"

At this time the titpetric/netdata image is not compiled with support for dbengine. There is an open issue and PR about it on github.

On 11/3/2019 at 10:45 PM, primeval_god said:

At this time the titpetric/netdata image is not compiled with support for dbengine. There is an open issue and PR about it on github.

@Gyurci Good news, the PR landed today. dbengine should now be usable if you pull the latest titpetric/netdata image.

@primeval_god Thanks, thats very good news. I will give it a try again.

 

edit: Looks like it is working perfectly!

Edited November 8, 20196 yr by Gyurci

On 11/8/2019 at 3:10 AM, primeval_god said:

@Gyurci Good news, the PR landed today. dbengine should now be usable if you pull the latest titpetric/netdata image.

@primeval_god After a day of testing this, it is not working as it should. I now have graphs back about 5hours. But I configured the dbengine cache size to 4GB and it runs from about 23hours ago, the cache file size is now about 18MB only.
I added a new path to the docker container: /var/cache/netdata (container) -> /mnt/user/appdata/netdata/cache/ (host)
It is working correctly, because I can see the generated dbengine files in my appdata/netdata/cache/dbengine folder.
 

But, in the meantime there was an update to the container and I set the docker auto update to run at 6am and my graphs are persistent back exactly to the same time! So I think, when the docker update invoked, it is cleared my dbengine cache completly. How can I resolve this issue? Can I configure the docker somehow for not touching the dbengine cache folder when an update is invoked?

Ok, I looked through the global section of the netdata config file and found this: delete obsolete charts files = yes

I set this to "no" and restarted the docker. Maybe this prevent the system from deleting the cache files??? Now testing with this until the next update...

On 11/9/2019 at 11:08 AM, Gyurci said:

Ok, I looked through the global section of the netdata config file and found this: delete obsolete charts files = yes

I set this to "no" and restarted the docker. Maybe this prevent the system from deleting the cache files??? Now testing with this until the next update...

There was an update for the container midnight and my server auto updated at 6am without problems, and looks like my dbengine database files are persistent now. So looks like the "delete obsolete charts files = no" setting solved the problem.