celesteking

Click on "Trigger condition" "**Info**" link and you'll be presented with available data. Assuming the Monitor has been created by extraction query method.

Well, just found out that Mustache is being executed on client side and the relevant call to ES server is via `/api/alerting/monitors/_execute` which returns JSON with `ctx.results` in Mustache pinned...

Please move this issue over to [kibana plugin repo](https://github.com/opendistro-for-elasticsearch/alerting-kibana-plugin/issues). Thanks.

SRPM of e.g., this: [opendistroforelasticsearch-kibana-1.13.2-1.x86_64](https://d3g5vo6xdbdb9a.cloudfront.net/yum/noarch/opendistroforelasticsearch-kibana-1.13.2-linux-x64.rpm) **update**: I was able to apply my changes by manually editing `/usr/share/kibana/plugins/opendistroAlertingKibana/target/public/opendistroAlertingKibana.chunk.2.js` and then gzip & brotli ' ing the resulting file.

In my case (Angular 6 -> 6.1 LTS upgrade), it was [because some idiot added](https://github.com/celesteking/fraudmarc-ce/blob/7fc769baf5553b6f7df1c0ded9c6a8a364ae9fa1/frontend/src/index.html#L65) `window.global = {window};` to `index.html`. Removing that cleared the error. Spent 4 hours trying to...

In order to make wildcard matches work, you should use: ``` input: '{"param":".+"}' ``` This lib is badly coded, very convoluted.

Yes, it is. your code is very hard to read. You should read a book on programming styles and another one on patterns.

How come this prevents server from processing the request? This must not happen. It's spitting HTTP 500 instead of just carrying on, even though `SecRequestBodyLimitAction` has been set to `ProcessPartial`....

Absolutely terrible backblaze s3fs / b2 s3fs / backblaze linux mount support. Same problem with the same multiple created versions as described above (your cost would be multitude $$). Backblaze...

Twilio doesn't give a shit. It's no longer a dev first platform.