@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.

@nurr said in How to simulate system events?:

rest.testMode=false

What version of Mango are you using? In 4.0 rest.testMode=false has been replaced by the testing. settings.

Yes. You can always import from an older system into a newer one but not backwards. Since this is a beta release you may find bugs, if you do please post them back here in the forum so we can fix them.

@AldoRamos I would first confirm that the Unit on the mysterious point is the same as the Rendered Unit. If not Mango will convert from one unit to another. Just a thought.

The defaults that will be used if no property exists are:

lineProtocol.task.queueWarningSize: 10000
lineProtocol.pointValidation.cacheExpirySeconds: 5000

Basically you will have to experiment with your setup and these would only need to be adjusted when you see performance degradation.

@jmatesanz after further investigation you can configure this in the connection URL. See all the connection properties here:

https://docs.microsoft.com/en-us/sql/connect/jdbc/setting-the-connection-properties?view=sql-server-ver15

Specifically

loginTimeout

@jmatesanz there is currently no setting for this on the SQL Data Source. The timeout will default to no timeout ever.

@cmusselm The Modbus slave monitor points only update if the status of the slave changes. They are not set to true on every successful poll.

I would play around with not updating on context but instead run the meta point every minute.

@cmusselm the JSON Retriever data source will definitely use the time supplied if it is parsed from the message correctly. If the parsing fails you should see a "Parse Exception" event raised. In that situation it will use Mango's poll time as the timestamp for the value. I would triple check your settings on the data source.

@cmusselm

What doesn’t make sense to me is that if it really does this, then why isn’t every event created and every data point’s time stamp future dated? This only happened 3 times in ~20 on event creation from the detector. Something seems off with that.

I can't speak to this but I would assume that the time you are receiving is different to what you think (or out of order)

Also, if I’m getting the date/time stamp from the JSON feed, should the data point details show the time as the JSON feed’s time? That isn’t what I’m seeing, the data point time is in my account’s time zone.

The Mango UI will render the time in the timezone setup for the system or logged in user if it is set.

In the screenshot below there should be values between the 4:21pm and 8:49pm timestamp. The data point is set to log when the point timestamp changes, so even if we log the same value it should still log and show up shouldn’t it?

I should have been more specific. Depending on the logging type of the point "backdated" values are handled differently. I tend to use Log All data points which will log everything. These types will ignore backdates:

• On Timestamp Change
• On Change
• On Change Interval
• Interval