@CraigWeb We just tried to make this change and I noticed a couple of things.
There is no option for setting intervalLoggingType once you've set loggingType to "Interval and when point value changes" via the GUI.

We ended up just changing the JSON and pushing that out, which it seems to have taken the changes.

Also interesting, when hitting the API endpoint for data point details...if the point is configured as ON_CHANGE_INTERVAL it does not return a key for "intervalLoggingType" nor is any value for any keys set to "AVERAGE" but I certainly do see those for points configured as "INTERVAL"

I honestly always assumed the way ON_CHANGE_INTERVAL worked was it logs on changes and the current value once per minute, I had no idea this would be averaging over that minute and then recording the average.

Anyway...I'll let you know the results, just wanted to give that info.

@CraigWeb We just tried to make this change and I noticed a couple of things.
There is no option for setting intervalLoggingType once you've set loggingType to "Interval and when point value changes" via the GUI.

We ended up just changing the JSON and pushing that out, which it seems to have taken the changes.

Also interesting, when hitting the API endpoint for data point details...if the point is configured as ON_CHANGE_INTERVAL it does not return a key for "intervalLoggingType" nor is any value for any keys set to "AVERAGE" but I certainly do see those for points configured as "INTERVAL"

I honestly always assumed the way ON_CHANGE_INTERVAL worked was it logs on changes and the current value once per minute, I had no idea this would be averaging over that minute and then recording the average.

Anyway...I'll let you know the results, just wanted to give that info.

@CraigWeb wow, I didn't even notice that. I'll let you know how it goes.

@CraigWeb

We do have a few instances of mango with higher thread counts than 100 but I've never ran in to that bug as of yet. If it comes to it, we can do and upgrade to see if that helps.

The datasource is modbus set to poll every second.

{
  "dataPoints":[
    {
      "xid":"Lorem_IPSUM",
      "name":"IPSUM",
      "enabled":true,
      "loggingType":"ON_CHANGE_INTERVAL",
      "intervalLoggingPeriodType":"MINUTES",
      "intervalLoggingType":"AVERAGE",
      "purgeType":"YEARS",
      "pointLocator":{
        "range":"HOLDING_REGISTER",
        "modbusDataType":"TWO_BYTE_INT_UNSIGNED",
        "writeType":"NOT_SETTABLE",
        "additive":0.0,
        "bit":0,
        "charset":"ASCII",
        "multiplier":1.0,
        "multistateNumeric":false,
        "offset":1000,
        "registerCount":0,
        "slaveId":1,
        "slaveMonitor":false
      },
      "eventDetectors":[
      ],
      "plotType":"SPLINE",
      "rollup":"NONE",
      "unit":"",
      "simplifyType":"NONE",
      "chartColour":"",
      "chartRenderer":{
        "type":"IMAGE",
        "timePeriodType":"DAYS",
        "numberOfPeriods":1
      },
      "dataSourceXid":"Lorem_DS",
      "defaultCacheSize":1,
      "deviceName":"Lorem",
      "discardExtremeValues":false,
      "discardHighLimit":1.7976931348623157E308,
      "discardLowLimit":-1.7976931348623157E308,
      "intervalLoggingPeriod":1,
      "intervalLoggingSampleWindowSize":0,
      "overrideIntervalLoggingSamples":false,
      "preventSetExtremeValues":false,
      "purgeOverride":false,
      "purgePeriod":1,
      "readPermission":"dolor,sit",
      "setExtremeHighLimit":1.7976931348623157E308,
      "setExtremeLowLimit":-1.7976931348623157E308,
      "setPermission":"",
      "tags":{
      },
      "textRenderer":{
        "type":"ANALOG",
        "useUnitAsSuffix":true,
        "format":"0.00"
      },
      "tolerance":0.0
    }
  ]
}

@CraigWeb

Hi Craig, unfortunately that metric was behaving as I would expect; climbing a bit and then dropping to 0.

This instance has 501 points and is running on the same hardware as a RD121C except we only have 4GB of ram. The instance had its threads set to 100 and I increase that to 200 but it made no difference at the time. We have since restarted the data points so we will see if it prevents the issue in the future.

In the mean time, we have a lot of sites to go through and look for this issue but we'll keep one in this state to continue troubleshooting.

Hello, I just recently noticed that some of our points that are configured as ON_CHANGE_INTERVAL are not logging properly on Mango 3.7.4

I am at the beginning stages of looking in to this so I don't know exactly how widespread the problem nor all of the variables but we have a couple dozen points set up to log when the point value changes and every minute regardless of if there is a change. It appears to just stop logging every minute but will eventually start again. It seems to start logging again when a change occurs but other times it appears to be random. I do not see any errors in the ma.log and it doesn't seem to be happening on every point configured as OCI.

We poll more frequently than we log and I can see the values from each poll that is occurring from the cached list but it just doesn't seem to log even though it is polling fine.

I can see that the points that are having an issue DO NOT have an Interval Logging job entry in the high priority queue. Disabling and enabling the point does seem to work but I am hoping someone could offer a little bit of insight as to why and how we can fix this.

Thanks,
Ed

Good Morning IA,

I have created a new user but they seem to be unable to see older events that were raised prior to the user being created.

This new user has superadmin, same as me, but I am able to see the events, and he is not.

Ed

Sure!

{
         "xid":"EH_964391",
         "alias":"",
         "handlerType":"EMAIL",
         "eventTypes":[
            {
               "sourceType":"DATA_POINT",
               "dataPointXID":"siteName_Error_Log",
               "detectorXID":null
            }
         ],
         "activeRecipients":[
            {
               "recipientType":"MAILING_LIST",
               "mailingList":"ML_277765"
            }
         ],
         "sendEscalation":false
		 "escalationRecipients":[],
         "sendInactive":false,
         "includeSystemInformation":false,
         "includePointValueCount":10,
         "includeLogfile":false,
         "customTemplate":null,
         "additionalContext":[
         ],
         "script":null,
         "scriptPermissions":{
            "scriptDataPointReadPermission":"",
            "scriptDataPointSetPermission":"",
            "scriptDataSourcePermission":""
         },
         "disabled":false
      }

I did already blow them out of the system, I just happen to have a bad tab habit so it was still in Np++.

So now it is complaining about inactiveRecepients.

{
  "cause" : "IOException: com.fasterxml.jackson.databind.JsonMappingException: (was java.lang.NullPointerException) (through reference chain: com.serotonin.m2m2.web.mvc.rest.v1.model.events.handlers.EmailEventHandlerModel[\"inactiveRecipients\"])",
  "mangoStatusName" : null,
  "mangoStatusCode" : -1,
  "localizedMessage" : "Internal Server Error"
}

ERROR 2019-03-21T09:22:12,078 (com.infiniteautomation.mango.db.query.StreamableSqlQuery.query:93) - (was java.lang.NullPointerException) (through reference chain: com.serotonin.m2m2.web.mvc.rest.v1.model.events.handlers.EmailEventHandlerModel["inactiveRecipients"]) com.fasterxml.jackson.databind.JsonMappingException: (was java.lang.NullPointerException) (through reference chain: com.serotonin.m2m2.web.mvc.rest.v1.model.events.handlers.EmailEventHandlerModel["inactiveRecipients"])

ERROR 2019-03-21T09:22:12,079 (com.infiniteautomation.mango.db.query.StreamableSqlQuery.query:101) - (was java.lang.NullPointerException) (through reference chain: com.serotonin.m2m2.web.mvc.rest.v1.model.events.handlers.EmailEventHandlerModel["inactiveRecipients"]) For Query: SELECT eh.id,eh.xid,eh.alias,eh.eventHandlerType,eh.data FROM eventHandlers AS eh com.fasterxml.jackson.databind.JsonMappingException: (was java.lang.NullPointerException) (through reference chain: com.serotonin.m2m2.web.mvc.rest.v1.model.events.handlers.EmailEventHandlerModel["inactiveRecipients"])

I believe all of the handlers are set as "sendInactive":true, "inactiveOverride":false.

Did I need to basically do the same thing as yesterday?

Find: "inactiveOverride":false,
Replace: "inactiveOverride":true, "inactiveRecipients":[],

And then change it back?

So upon further investigation it looks like these may have been changed over time or something? I'm not really sure, but it looks like each, expect for 1 or 2, of the ones that complained about the detectorXID have a near identical event handler set up that is valid and functional.

I'm going to go ahead and delete them via the API.

I exported the event handler JSON to make some changes and after importing the changes I was thrown a couple of these errors.

Event handler 'EH_964391': Event type must have a 'detectorXID'

The exported JSON shows "detectorXID":null

It even shows me the e-mail lists and it says it is not disabled.

The GUI, however, doesn't show that I have any e-mail set up for the even that would trigger it.