bosun | Time Series Alerting Framework | Monitoring library

I had the same problem and I discovered that this is a bug of Kotlin library. (I am so serious.) You cannot call intArrayOf() method.

I am sure that you are using Windows 10 Single Language Turkish. (I was using the same operating system.) Kotlin's some libraries cannot work on Turkish operating system. You can check this issue on YouTrack.

You can solve your problem with installing Windows 10 Pro English or Windows 10 Single Language English. I do not know any other approach right now. (You can open new issue on Kotlin website.)

This bug took from me 30 days. You can check my related question about this Kotlin bug.

If you're really not interested whether or not your alert condition is met during certain times, you could introduce an additional condition to your alerts and make use of the epoch() function. epoch() returns the current timestamp at the evaluation of the alerts. Then add that to the crit or warn condition. Something like this will work:

I would guess the OS is not accepting this as a proper executable?

1. If a binary, did you compile it on the same system, or make sure your cross compiled it for the right architecture?

2. If a script, does your script have the bang line at the start, for example #!/bin/bash?

It seems that this transformation is about applying aggregation to the first derivative. Here's an example using win.disk.duration metric from scollector but on a different backend.

1. Raw data represents a counter with reset.
2. First derivative calculates the rate of change over a user-defined interval (1 second). Negative delta is handled as a reset by default, but this behavior can be controlled with rate-counter=true|false parameter.
3. The aggregation function max is applied to the rate over a user-defined period (5 minutes).

I would recommend using 95 percentile function instead of max however. The p95 statistic allows you to discards infrequent spikes from analysis.

Disclaimer: I work for Axibase.

Both of these features are mostly scollector specific. The "host" view (I've considered ripping that out, it was done in the early days, better to use something like grafana) depends on scollector specific metrics such as os.cpu.

As far as "Auto" for rate vs gauge, that is also metadata that comes from scollector and sent to bosun. If you want to try to mimic the behavior see https://github.com/bosun-monitor/bosun/blob/master/metadata/metadata.go#L30 and https://github.com/bosun-monitor/bosun/blob/master/metadata/metadata.go#L195 - you would need to create at least the "rate" key for each metric you are getting from telegraph.

Since q() is specific to querying OpenTSDB, it uses the same syntax. The basic syntax for what you put would be to use a pipe symbol: ungroup(avg(q("sum:metric.name.hrsp_2xx{region=eu-west-1|eu-central-one}", "1m", ""))).

If you have version 2.2 set to true you can also use more advanced features of the filters as documented in the OpenTSDB documentation (i.e. host=literal_or(web01|web02|web03)). The main advantage is that OpenTSDB added the ability to aggregate a subset of tag values instead of all or nothing. The Graph page in Bosun also helps you generate the queries for OpenTSDB.

In your situation there are 3 aspects to monitor:

1. Have the jobs run
2. Did the jobs run with a successful result
3. Did the jobs run with a unsuccessful result

Elastic doesn't matter in this case, so I have simulated the responses with the series function: