To use a specific Timezone:

DateTimeFormatter dateTimeFormatter = DateTimeFormat.forPattern("MM/dd/yyyy HH:mm").withZone(DateTimeZone.UTC);

Hi All,

Just wanted to let you know we have updated our developers documentation. We have separated it into 2 parts, Angular for the UI and Java for the backend. As of Mango 3.7 there is a new 'development' mode that can save time developing. Check them out here:

UI Development Process

Eclipse for Java

xbastek,

You say:

But i don't know how to update this files in my mango installation...

It will be far easier for you to upgrade to Mango 2.6.0 that has all the work done for you. It will be pre-released very soon.

Thanks,
Terry

@nachum37 thanks for making us aware of this, I will take the information you provided here and have our team replicate what is happening so we can fix any problems we find.

I wrote this help article not too long ago which may provide some insight into configuring the Apache proxy.

https://help.infiniteautomation.com/proxy

Sorry, our maven repository only holds the latest snapshot versions and lets the older ones roll off. The latest version is 3.6.1-SNAPSHOT for the api module. Since that version will also eventually drop off of the repository I would suggest you use the release version of the api module as that will always be available. So change the dependency from 3.6.0-SNAPSHOT to 3.6.0 and you should be good to go.

@Nurr

There is the possibility to use the Email Event handler to do this. If you return "CANCEL" from the script on an email event handler it won't actually send an email. Leveraging this one could write a script to make an SQL query for the numbers and then call your global script. You can call Java code directly from the script but it will require some knowledge of Java and how to use it within the Nashorn Javascript Engine. There should be some examples of this on our forum. Basically the script needs superadmin permission and you must use the full package and class name when you reference a Java class.

If you are game to give it a try, here is some documentation on the SQL api for Java:
https://docs.oracle.com/javase/tutorial/jdbc/basics/processingsqlstatements.html

As a side note Mango 4.0 will have a Message event handler that will allow using Twilio and in the future other platforms to send messages.

@BG I am pretty sure there will be no problems with the versions of MariaDB that support JSON columns. To make a long story short we have not tested it with MariaDB but the only place we use the JSON type column so far is in the create table script for the users table so the alias they have will be fine on that statement.

In the future we may actually create queries that introspect the data in that column but this will likely be for custom modules and not part of the standard Mango application. Also H2 does not support JSON column types so all of our queries basically use that column as a LONGTEXT type currently.

@MattFox just letting you know I've tried in the past to fix this but didn't have much luck. But I tried again today and managed to make an improvement. There are likely other models that will suffer from this problem so when Mango 3.7.0 is released if you see any more of these types of problems please let us know.

Here is the git issue if you are interested in following:

https://github.com/infiniteautomation/ma-modules-public/issues/72

Version 4.2.0

• Mango is now built for Java 11, it is now a hard requirement to use Java 11 or higher to run Mango
• Fix bugs in ipv6 network tools to accurately whitelist ipv6 addresses, would previously blacklist all ipv6
• Fix bugs when importing data points that include event detectors after exceeding the amount of data points allowed by the license
• Availability to monitor the common pool size inside ForkJoinPool, as an internal point for metrics.
• Fix bug in data point notify events to more accurately fire the correct event types that control meta points and event detectors
• Add properties to enable/disable disk usage monitoring for SQL and TSDB directories (internal.monitor.diskUsage.monitorSql and internal.monitor.diskUsage.monitorTsdb)
• Disable disk usage monitoring for SQL and TSDB directories by default
• Add property to enable/disable use of OSHI native library for metrics (internal.monitor.enableOperatingSystemInfo)
• Only get and update the process once when polling OSHI native library
• Remove system metrics that called getAllStackTraces(): com.serotonin.m2m2.rt.maint.WorkItemMonitor.maxStackHeight and com.serotonin.m2m2.rt.maint.WorkItemMonitor.threadCount
• Dont allow concurrent polling for metrics in ServerMonitoringService and DiskMonitoringService
• Fix bug where "sessionCookie.persistPeriodSeconds" setting was ignored
• Add setup page to configure admin password and locale on first login
• Move timezone env property use to be before Logging initializes so logging uses this timezone
• Add comma separated env property for MySQL backups to allow passing options to mysqldump, for large systems use db.mysql.extraDumpArgs=--single-transaction,--skip-lock-tables

@robmalone yes, the Script data source and Meta data points retain state while they are enabled. This means you could create an array that exists while the source/point is running to store failed messages. On each run you would check the array and if not empty then try to resend the messages.

Just remember if you stop the point or data source that array will go away. If you need more resilience you could attempt to store the messages, that will be much more complex but is possible.

@cmusselm that is one of the shard files that Mango stores its time series data in. It would have been created by Mango. I don't use Windows but a similar situation in Linux will occur if you started Mango as root, then stopped it and restarted it as a user with less permissions.

This is not on the plans to change this functionality for Mango 4.

@nachum37 thanks for making us aware of this, I will take the information you provided here and have our team replicate what is happening so we can fix any problems we find.

What version of Mango are you using? What event handler type do you have configured? Email?

I have seen that happen when you have a trailing slash on the property. Make sure you have this exactly:

store.url=https://store.mango-os.com

@tped See this section:

Configuration file is now named mango.properties

On this link:
https://docs-v4.mango-os.com/upgrade-to-v4

@marganellim the script I gave you is for the "script" section of the email event handler. That is the only place the "model" is included in the script context as it is normally used to modify the model that is used to generate the Email via the FTL template but you can do anything you want in that script.

The script you use will depend on the type of Event Handler you choose. If you want to use a "Script" Event Handler then this would work:

/**
 * This script implements com.serotonin.m2m2.rt.event.handlers.EventHandlerInterface
 * Add this script to a "Script" type event handler and choose the Graal.js or Nashorn engine.
 */

/**
 * Called when the Mango event is raised.
 * You must implement this method.
 *
 * @param event
 */
function eventRaised(event) {
    console.log('Raised', event);
    console.log('test xid: ' + event.getContext().get('point').getXid());
}

/**
 * Called when the Mango event is acknowledged (the event may still be active).
 * Supported as of Mango v4.0.0-beta.14, you are not required to implement this method.
 *
 * @param event
 */
function eventAcknowledged(event) {
    console.log('Acknowledged', event);
}

/**
 * Called when the Mango event returns to normal or is deactivated (e.g. on shutdown).
 * You must implement this method.
 *
 * @param event
 */
function eventInactive(event) {
    console.log('Inactive', event);
}

In Mango 4 this script:

LOG.info('Source point xid: ' + model.point.xid);
LOG.info('Source detector xid: ' + model.pointEventDetector.xid);

return UNCHANGED;

Produces this output:

INFO 2021-10-25 08:29:09,725 - Source point xid: DP_495b84f1-ecda-4aef-9486-fa91b92c48e6
INFO 2021-10-25 08:29:09,738 - Source detector xid: ED_31d340c1-a979-4eba-b0c6-71eca7c50787

@Ricardo thanks, that all looks ok to me. Basically what is happening is that Mango uses a pool of TCP/IP connections to the database and when choosing one to use it tests it first to ensure it is still connected. In this case Mango sees that the connection is broken and the database pool library (Hikari) is logging that.

For some reason the database connections that Mango is opening are being closed. This is not normal. From your log posting I can see that the delay is pretty close to 10 minutes, so I would be looking for any settings between Mango and your MySQL server that timeout at 10 minutes. It is possible you have a Proxy or Firewall between the 2 that is severing the connections at 10 minutes...

If none of that helps then I suggest you post the mango.properties for your database. The begin like this:

# MySQL database settings. Your MySQL instance must already be running and configured before this can be used.
db.type=mysql
...