Daniel Mitterdorfer
Daniel Mitterdorfer
The URLs depend on what requests Kibana sends for these benchmarks and that can change as Kibana adopts new Elasticsearch APIs. Our plan was to cast a wide net so...
That's odd. I ran `csysdig -r trace.scap` on the machine where I have created the trace file and it presented at least an initial screen (so I did not get...
> What version of sysdig do you have on your VM (and where you use csysdig if different)? This was probably lost in all the information provided in the original...
Oh sorry! I was under the impression that I have already the latest version as I installed it just recently. I'll update soon and report my findings.
I've downloaded the [Debian x86_64 package for sysdig 0.19.1](https://s3.amazonaws.com/download.draios.com/stable/deb/stable-amd64/sysdig-0.19.1-x86_64.deb). The download URL for the Debian package at https://www.sysdig.org/wiki/latest-packages/ reports 0.17.0 as latest version but given your hint, I just adjusted...
@obfischer: Just as an idea: We've solved this using Maven profiles: https://github.com/elastic/elasticsearch/blob/2.x/distribution/pom.xml#L292-L321 - but we have a separate subproject just for RPMs so that's pretty easy for us.
@b-deam there is currently also another issue with the existing usage of `es.options()` that I stumbled upon. The current calls to `es.options()` (see https://github.com/elastic/rally/pull/1705/files) are ineffective because `options` returns a...
I've marked this issue as "blocked" as multiple data paths are still allowed in Elasticsearch 8.0 with https://github.com/elastic/elasticsearch/pull/78031 (the feature remains deprecated though).
As far as I understand the proposal, tagging commits would solve the issue on the `master` branch on `rally-tracks` (or `rally-teams`) but not necessarily on any other branch in these...
The existing telemetry device `ClusterEnvironmentInfo` already extracts data from node stats and attaches it as meta-info to metrics documents. There are two different levels: `cluster` and `node` and only cluster-level...