Rally benchmark aws.ec2 logs#8416
Conversation
|
/test |
🌐 Coverage report
|
| value: "da6cb4c8-c84c-4c5f-97c7-f8586a098af4" | ||
| - name: cloud.region | ||
| enum: ["us-east-1", "us-east-2", "us-west-1", "us-west-2", "ap-south-1", "ap-northeast-3", "ap-northeast-2", "ap-southeast-1", "ap-southeast-2", "ap-northeast-1", "ca-central-1", "eu-central-1", "eu-west-1", "eu-west-2", "eu-west-3", "eu-north-1", "sa-east-1", "af-south-1", "ap-east-1", "ap-south-2", "ap-southeast-3", "eu-south-2", "eu-central-2", "me-south-1", "me-central-1"] | ||
| cardinality: 100 |
There was a problem hiding this comment.
same question here as in the other PR - how can a field have cardinality of 100, when it has fewer possible values?
There was a problem hiding this comment.
wanted to follow up on this cardinality value - where does 100 come from?
There was a problem hiding this comment.
I just want to have 100 ec2 instances (aws.cloudwatch.log_stream/host.name/aws.ec2.ip_address): since cloud.region is an enum with length 25, 100 itself is the LCM
There was a problem hiding this comment.
so if you didn't specify this - you would end up with 25 unique instances? by specifying this, for each region, you generate 4 unique values of the log_stream, host.name and ip_address, resulting in 100 unique instances?
|
@tommyers-elastic all good here? :) |
|
@elastic/ecosystem I'd need your CR |
Enhancement
Proposed commit message
Add artifacts for
elastic-packagerally benchmarkChecklist
- [ ] I have added an entry to my package'schangelog.ymlfile.- [ ] I have verified that Kibana version constraints are current according to guidelines.Author's Checklist
How to test this PR locally
Checkout branch from elastic/elastic-package#1522, build
elastic-packageand execute fromawspackage root (remember to bring up the elastic-package stack before):./elastic-package benchmark rally --benchmark ec2logs-benchmark -vRelated issues
Screenshots