Please Note This forum exists for community support for the Mango product family and the Radix IoT Platform. Although Radix IoT employees participate in this forum from time to time, there is no guarantee of a response to anything posted here, nor can Radix IoT, LLC guarantee the accuracy of any information expressed or conveyed. Specific project questions from customers with active support contracts are asked to send requests to support@radixiot.com.

@Ricardo there is some information here as to how to use iptables. I suggest you familiarize yourself with how they work as they are useful to redirect port I/O between privileged ports and non-privileged ports.

https://docs-v3.mango-os.com/linux-security

@ricardo
Try the 'No change' event detector or others as shown below:

00010f54-4fd9-43fb-bb3f-46305a54e016-image.png

@MattFox @Elena Hi!

We made changes then restarted Mango (both v3.7.7 and 4.0.0.beta3). Mango forced the user to log in again. But it doesn't consider user inactivity. Even if the user is actively working, Mango forces to log out after a period of time.

Timestamp in this instance should be a unix timestamp unless you configure custom categories for the x axis.

Fox

It is an operating system permission, not a MySQL permission

@Nurr for this to work you will want to start up Mango 3.7.7 on the old database and then upgrade to Mango 4.0.0. We do not support restoring Mango 3.7.x on top of a new Mango 4.0.o database.

Hi @Dave-Frazier !

Any update for the topic?

Thanks in advance,

Hi @terrypacker ,

Although we upgraded v3.7.7 to v.4.0.0.beta2, it is still written ' rest.testMode=false ' on the env.properties file.

Hi @Dave-Frazier ,
Additionally, can please share documentation for /rest/latest/testing/raise-event ? How can I use it?

Thanks!

Hey Craig, Thanks for all the help.
I ended up figuring it out :)

<md-card flex=""> <md-card-content> <ma-get-point-value point-xid="UAR-STN-DP_Gen_BreakerState" point="point1"></ma-get-point-value> <ma-get-point-value point-xid="UAR-STN-DP_Gen_State" point="point2"></ma-get-point-value> <ma-point-values point="point1" values="point1Values" from="dateBar.to | maMoment:'subtract':1:'day'" to="dateBar.to" rollup="FIRST" rollup-interval="1 hours"> </ma-point-values> <ma-point-values point="point2" values="point2Values" from="dateBar.to | maMoment:'subtract':1:'day'" to="dateBar.to" rollup="FIRST" rollup-interval="1 hours"> </ma-point-values> <ma-state-chart style="height: 500px; width: 100%" series-1-title="{{point1.name}}" series-1-values="point1Values" series-1-labels="point1.getTextRenderer().values" series-2-title="{{point2.name}}" series-2-values="point2Values" series-2-labels="point2.getTextRenderer().values"> </ma-state-chart> </md-card-content> </md-card>

As long as your system configuration hasn't changed you will be fine.

@jcaballeroa I was able to replicate it, there is a bug. Once the bug is fixed it will be announced in the forum.

Hello, Thanks for your replies, I tried @Ralf suggestion and I think is all right. Thanks!

@Nurr
The Mango NoSQL stores +-50 million historical values per 1GB.

Any new ideas for this? I've just come back to the topic so was wondering if anyone had any insights?

I've written something to do this in the dashboard as a userModule component, but it'd probably be labourious doing it for each point...
But it allowed me to export all of the data from now till some time prior and generate a CSV that I could use to import the data with the new XID. However it still meant mapping the current point name with the new point name...
If that interests you, let me know.
Might be good to tweak it to automate it further for future ease of use....

Fox