Negative values in pipeline rules throughput about graylog2-server HOT 2 OPEN

#19696 may be related too?

from graylog2-server.

My original theory had something to do with a number being too large for its data type, such as a number > 2,147,483,647 for a signed 32bit data type. I'm not sure if that is relevant though.

The other thing i am noticing, which i can reproduce somewhat consistently, is how the graylog shows a much larger value initially before showing the accurate metric. I suspect this is showing the "total" amount since the amount rather than the accurate metric.

For example, i can sometimes get my pipeline to display a number of about 7 million, which matches up with the metric's total value:

{
    "full_name": "org.graylog.plugins.pipelineprocessor.ast.Pipeline.62976aa4578cf42110255552.executed",
    "metric": {
        "rate": {
            "total": 7189178,
            "mean": 88.88558165055522,
            "five_minute": 111.75158774985267,
            "fifteen_minute": 114.95970546937819,
            "one_minute": 102.30150129886736
        },
        "rate_unit": "events/second"
    },
    "name": "executed",
    "type": "meter"
}

In the video below i am boing back/forward in the browser to trigger this behavior:

https://videos.graylog.com/watch/VTdQfbzHSvgFAA6n2r4AM1?

Its not clear if this is the same issue or not. It also appears the metric rate calculation is being done on the front end?

from graylog2-server.