[Rally] Add benchmarking templates to data streams for set of packages

[ali786XI]

As per the main Meta issue, need to add benchmarks to integrations. Initially adding one log ( nginx.error ) and one metric ( mysql.performance ) data streams as per discussion with @lalit-satapathy .

Nginx

Preview Give feedback

1. nginx.error - PR
2. nginx.access - PR
3. nginx.stubstatus - PR

MySQL

Preview Give feedback

1. mysql.performance - PR
2. mysql.error - PR
3. mysql.galera_status - PR
4. mysql.slowlog - PR
5. mysql.status - PR

[tommyers-elastic]

it's fine to use this issue for more granular internal tracking, but please ensure the parent meta issue is updated too as this work progresses. :)

[ali786XI]

it's fine to use this issue for more granular internal tracking, but please ensure the parent meta issue is updated too as this work progresses. :)

Sure I'll update the main Meta as well as so as to keep in sync

[agithomas]

@tommyers-elastic / @ruflin ,

Is the final goal to have Rally benchmarking for all integrations (including AWS / GCP / Azure integration packages)?

[tommyers-elastic]

i don't think that's realistic - but i think we should have benchmarks for our most popular/valuable integrations.

[agithomas]

i don't think that's realistic - but i think we should have benchmarks for our most popular/valuable integrations.

When we did the TSDB enablement, aligned certain integrations as P0 priority. If my understanding is right, the priority is defined based on the usage stats. Can those priority assignments be considered here as well?

[ruflin]

Can those priority assignments be considered here as well?

I think the simple answer is yes. We should look at it case by case but the P0 integrations should also be the one where we fully understand changes and how they perform.

[lalit-satapathy]

Any suggestions, should we keep this low level issue going forward as there is also another top level issue existing for tracking the rally enablement. Or should these be merged?

[ruflin]

I suggest we merge into #8636 as I assume this one is a subset of the other one? Happy to keep this one until PR's are merged.

I like how the tracking is added to this issue, maybe we can do the same for the other?

[ali786XI]

Closing this issue as we have the Main meta to track all the benchmarking PRs.
cc:- @lalit-satapathy