elastic

The API happily accepts attribute updates for host_name and service_name of Downtime objects. That doesn't sound like a good idea to me, just look at the inconsistency between the object name and its attributes in the console transcript below.

I haven't checked any other object types for similar issues, so there might be more as well.

$ downtime=$(curl -skSu root:icinga -H 

I have an application which receives log messages from a firewall. The logs are written into a MongoDB. My goal is to process 30'000 messages per second (more or less constantly for 7*24 hours, not as transient peak value)
As peak value I expect app. 50'000 messages per second.

With several settings I reached up to 20'000 msg/sec. but that is not sufficient for our life traffic. The MongoDB ho

Update scripts to setup RoadRunner or Swoole to utilize Laravel Octane.

https://github.com/laravel/octane
https://beyondco.de/blog/laravel-octane-introduction

Describe the bug
Passing a single row of data with a time scale on the X-axis breaks the chart.

To Reproduce
Go to https://codesandbox.io/s/cool-sound-8j9m7?file=/src/App.tsx

Notice by not setting the xDomain with a single values, causes the error below.

Expected behaviour
The chart is rendered with a single row of data

**Version (please complete the following info

Given an elasticsearch target, namespaced into a sub-path by nginx,
when I pass the full host+path into Elastix.Search.search (and other functions also)
then the path component of the elasticsearch url is stripped away.

I believe this code is problematic, in search.ex

def make_path(index, types, query_params, api_type \\ "_search") do
    path_root = "/#{index}"

When the inde