Do not follow where the path may lead; go instead where there is no path.
And leave a trail - Muriel Strode
No, you'll have to make your own watchlist page. But since it's made up of a lot of core elements without much code, you could replicate it yourself. You'd have to replace <ma-watch-list-chart> with your own ma-serial-chart and apply similar parameters plus the changes you want though.
Depends if the want outweighs the need. I'd argue this isn't much of an issue rather than being a means to display watchlist values. If you want something more specific you're going to need to leverage the dashboard designer or implement some custom code.
That's my take on it.
EDIT: I've read the components section under api help. There is an additional option to set options for the ma-watch-list-chart:
ui/docs/ng-mango/ma-watch-list-chart options (optional) object extend AmCharts configuration object for customizing design of the chart (see amCharts)
So it was pulled out for you to amend. Basically means you can make custom watchlist pages with the designer. No problems whatsoever.
You need to set a valueAxes option:
If autoGridCount is not set to false it ignores your preferred grid count setting.
So under options you'll need:
Depending on the number of axes you're using.
Hope that solves your conundrum
I would be interested to find out if there is a configuration problem here or if Mango could be doing something better.
Can you confirm:
- You are using MySQL
- The results of this query on that MySQL instance:
- The version of MySQL
- That /mysql/datadir does exist
- That the user running Mango has read access to /mysql/datadir
Then I can provide more specific help I think.
- Yes, 5.7.25 on a separate dedicated mysql server
- SELECT @@DATADIR
- as above 5.7.25
- There is no
- err looks like mango is running as root...
Trying to do a restore nosql db complete backup. ver 3.7.7
And mango crashes and I receive this error:
ERROR 2020-07-31T00:36:41,201 (com.infiniteautomation.mango.spring.components.DiskUsageMonitoringService.doPoll:159) - Unable to get Filestore partition usage java.nio.file.NoSuchFileException: /mysql/datadir at sun.nio.fs.UnixException.translateToIOException(UnixException.java:86) ~[?:1.8.0_171] at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:102) ~[?:1.8.0_171] at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:107) ~[?:1.8.0_171] at sun.nio.fs.UnixFileStore.devFor(UnixFileStore.java:57) ~[?:1.8.0_171] at sun.nio.fs.UnixFileStore.<init>(UnixFileStore.java:64) ~[?:1.8.0_171] at sun.nio.fs.LinuxFileStore.<init>(LinuxFileStore.java:44) ~[?:1.8.0_171] at sun.nio.fs.LinuxFileSystemProvider.getFileStore(LinuxFileSystemProvider.java:51) ~[?:1.8.0_171] at sun.nio.fs.LinuxFileSystemProvider.getFileStore(LinuxFileSystemProvider.java:39) ~[?:1.8.0_171] at sun.nio.fs.UnixFileSystemProvider.getFileStore(UnixFileSystemProvider.java:368) ~[?:1.8.0_171] at java.nio.file.Files.getFileStore(Files.java:1461) ~[?:1.8.0_171] at com.infiniteautomation.mango.spring.components.DiskUsageMonitoringService.doPoll(DiskUsageMonitoringService.java:155) ~[mango-3.7.7.jar:?] at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [?:1.8.0_171] at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) [?:1.8.0_171] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) [?:1.8.0_171] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) [?:1.8.0_171] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:1.8.0_171] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:1.8.0_171] at java.lang.Thread.run(Thread.java:748) [?:1.8.0_171]
EDIT: I realised I had accidentally clicked the incremental restore button. Don't know if that caused it but it may have something to do with trying to move 5GB of compressed NoSQL data...
Do some forum searching please.
replace pt.activeEvents with pt.value
Also, this post.shows.you how to iterate through point values...
Ah I see.. looks like this has changed a bit since I've last commented on that thread..
Sorry about that!
Let's use the events table component... I have no idea how well this will sit in amongst the table I provided! Some styling may be in order...
In fact... you may be able to replace my table tds in entirety with just one <td></td> and plonk this in the middle!
<ma-events-table single-point="true" point-id="pt.id" limit="5" active-status="'active'"></ma-events-table>
Use that in place of the ma-get-point-values, it's all written in the components api information in the dashboard menu.