@ottawa_admin on many linux distros resolv.conf tends to have a blurb similar to this "# This file is managed by man:systemd-resolved(8). Do not edit." I can't remember how the ES works but that's something that will burn you if it's not configured correctly.
Restarting the mango service itself would not affect it since this is a system level function. What you'd need to do is restart the whole ES so that Linux reboots and then have a look to see if your entries are still there.
Rather than hiding rows, it would be better to validate if these point values are changing, remove the ng-show and focus on the point values first. If they are not updating in realtime, then you have other problems.
@ua something else to note is that it appears you have a local device for each of your data sources. I'm not sure of your use case but it might work better if you share one local device across all of your data sources.
Thank you for your explaination. Can you be more specific about "datebar.to" and what is it in mango? I mean, there should be something like "myPoint.value" to show/assign a point value or "myDevice.name" to show the device name.
What version of Mango are you using: e.g. 3.7.7
What version of Java are you using: Oracle Java 8, or Adopt OpenJDK 11
What is your operating system: e.g. Windows x64, Ubuntu Linux 20.04
How did you install Mango: e.g. install script, or manual install, updated from 3.6.0
How did you start Mango: e.g. systemctl start mango, or ma.sh start
Include the log file: post ma.log
What browser are you using? e.g. Chrome 91.0.4472.124