• P
    PCM

    Extreme or incorrect values in the Mango data history have caused me a lot of problems (see the [url=http://mango.serotoninsoftware.com/forum/posts/list/1375.page Incorrect 0 point value...). We must have a way to locate and purge or modify selected data values in the PointValue history. I have deleted extreme values in the past via SQL, but these deletions are subject to errors (i.e. dangerous) and have often resulted in high-CPU usage problems that could only be rectified by restarting the Mango service.

    While the "Discard extreme values" datapoint function is useful, it has limitations:

    • It only applies to new values; it does not remove extreme values from the point history
    • In most cases the Discard feature is not enabled until extreme values have already been stored in the history
    • The discard value will not discard invalid 0.00000 values; it will only discard extreme values
    • If the Discard function is enabled, there is no way to detect the time, frequency, or value of the discarded data, which makes it difficult to troubleshoot and prevent extreme values from occurring in the future.[/list]
      It would be helpful if an optional alarm event were initiated each time an extreme value is discarded. The alarm would include the time stamp, the discarded value, and the discard threshold.

    What we need most of all is a point history editor that provides a means to select points based on their value and timestamp meeting certain criteria, and then either purge or modify those values (e.g. multiply or add to the point).

    posted in User help read more
  • P
    PCM

    Whether I create a new meta datapoint or edit an existing one, when I click on Generate History that icon blinks for a while, and then a pop-up window displays the number of points generated. The number of points generated seems to correspond to the "Update event" interval and the inception of the first input context point; the wait time also seems to correlate to the number of points generated. However, the "Point Details" page does not show the newly generated points: neither in the point history nor in the graph. I suspect that the point history is being generated but not stored in the database. I use this feature a lot, both when fine tuning formulas or when creating new meta datapoints. Can you please look into this ASAP?

    Relevant modules: core 2.0.6, meta 1.4.0

    On a related note, when I was using Mango 1.12.4, it seemed that I often had to purge all data before generating history. Does "generate history" always generate from Inception to Latest, or do I have to purge old data first? What time interval does it generate over if I already have points in the history?
    Thanks.

    posted in User help read more
  • P
    PCM

    I have an event detector that raises an alarm if the time stamp register value obtained from a data source does not change in more than one minute (I read that source every second, over Ethernet). Shortly after 3am almost every night, the following occurs:

    1. The time stamp unchanged alarm is raised,
    2. The CPU idle goes down
    3. CPU I/O wait goes up.
    4. Points to write goes way up
    5. Disk block writes goes up, but disk block reads goes way up
    6. Medium Priority Work Items shoots up from zero into the thousands

    Questions:

    1. What are these Medium Priority Work Items? Why is the peak number so different each night?
    2. How can I minimize the load or quantity of that 3am thread?
    3. Can Mango be modified so the Medium Priority Work Items are assigned a priority that is low enough to not interfere with data source reading?
    4. Can the Medium Priority Work items be staggered so they're not all submitted at 3am?
    5. Can Mango be modified so that reading a data source is assigned a higher priority thread?

    Thanks

    posted in User help read more
  • P
    PCM

    I must determine whether it is safe to grant write access to Internet Mango users without creating unnecessary risks. To implement this without adding too much danger, I must know whether common security features have been implemented.

    Which of the security features below have been implemented in Mango Automation 2.x?

    • Write failed login attempts to a log file, including originating IP address
    • Ban IP addresses with repeated login failures to prevent brute force attacks
    • Salt the passwords to prevent a break-in via a user with a weak password from making all other users vulnerable
    • Sanitize inputs to prevent SQL back door attacks as illustrated in [url=http://xkcd.com/327/]this cartoon

    image

    Thanks

    posted in Mango Automation general Discussion read more
  • P
    PCM

    How can I get the event email message subject to show the "alarm level" and "event message" (or event alias) rather than the id number?
    By message, I'm referring to whatever text is displayed on the Alarms page Message field:

    Pending alarms
    Acknowledge all Acknowledge all Silence all Silence all
    Id Alarm level Time Message Inactive time
    The problem is that all the subjects of emails sent via "User Details / Send alarm emails" currently look the same:
    Mango event active notification - id:<some_number>
    This is not informative, and I must open each email to find out what event occurred and what is the severity. It's too tedious to create an email event handler each time I add an event detector to a point; I would like the "Send alarm emails" setting in "User Details" to send the event "Alarm level" and "Message" in the subject field by default.

    I already copied
    /opt/mango/classes/i18n.properties to /opt/mango/overrides/properties/i18n.properties, but it is not obvious how I should change line 277-283.

    ftl.subject.default=Mango event {0} notification
    ftl.subject.default.id=Mango event {0} notification - id:{1}
    ftl.subject.alias={0} ({1})
    ftl.subject.alias.id={0} ({1}) - id:{2}
    ftl.subject.active=active
    ftl.subject.escalation=escalation
    ftl.subject.inactive=inactive
    

    Thanks.

    posted in User help read more
  • P
    PCM

    In the "Purge now" frame of a datapoint edit page there is a "purge now" button that purges value entries older than xx age.
    However, this does not allow point values to be purged conditionally based on their age or value. This is important because often we realize we need the "Discard extreme values" feature only in hindsight, after there has been a malfunction and the erroneous data is already stored in the point value database. It is also a problem because we may want the extreme values stored and plotted in order to troubleshoot them. For instance, if it weren't for plotting extreme values, I would not have realized that the import function was causing zero values to be stored in the point value database.

    Can you please include additional purge conditions in the "Purge now" frame?
    [list] Purge points between start time ss and end time ee[/list]
    [list] Purge points between start time ss and end time ee if value > A OR value < B[/list]
    [list] Purge points between start time ss and end time ee if value = 0
    [/list]
    Thanks

    posted in Wishlist read more
  • P
    PCM

    It would be good if XID import status were displayed in different colors: currently all import results display in red, so errors do not stand out.
    This is especially a problem when there are a lot of points.
    e.g.:
    red=errors,
    green=added new XID,
    blue=updated existing XID

    Thanks.

    posted in Wishlist read more
  • P
    PCM

    In M2M version 1.12.3 I could export point definitions, edit them, and then import them. This is useful for duplicating or changing multiple existing points. However, in MA version 2.0.3, whenever I import point definitions, erroneous 0 point values are stored in the datapoint value tables. This is of course a big problem for data integrity. Perhaps the RELEASE-NOTES file indicates when this problem crept in:

    Version 1.3.1
    Enhancements:

    • Don't disable data sources when importing data points
      Can you either roll back this feature, or at least make it optional on the import page so zeroes are not inserted into the point values tables?
      How can I search and purge points that meet a certain value? I purchased the SQL module.

    Thanks

    posted in User help read more
  • P
    PCM

    The metadata script:

    return WTenabled.past(HOUR, 1).get(true).proportion * 100; // % on last hour
    

    works in Mango 1.12.3, returning values between 0 and 100 inclusive depending on the past hour.

    However, it no longer works in MA 2.0: it returns: "Success. result=NaN"
    If I change get(true) to get(false):

    return WTenabled.past(HOUR, 1).get(false).proportion * 100; // % on last hour
    

    it returns: "Success. result=0.0"
    I wonder if the proportion code is missing a check for 0/0?

    posted in User help read more
  • P
    PCM

    Can you please ensure that the datapoint import routine will check to see if there is already a value for the given time stamp, and if so, overwrite the existing value instead of creating duplicate time entries with different values?

    This will not only prevent data duplication if an already-imported point time entry is re-imported, it may also provide an easy way to correct erroneous values that may have crept into the time history.

    Thanks.

    posted in Wishlist read more