...
- Set up Perf environment. This environment will be working all time and shared between a few teams, but only devops team should have permission to update and reconfigure this by request, but it is important to do it very quickly because performance testing is very time consuming and downtime during the next changes (configuring/updating the system, changing different parameters, changing the number of the Kafka topics, etc.) should be as little as possible. Some configuration examples: LCP performance testing, Folijet - Lotus Snapshot Performance testing
- Automatically create job profiles to DI (as usual we use PTF - Create 2 and Updates Success - 1 profiles). For this action, we can use Karate test and Jenkins job to start this test.
- Start one or more DIs in automatic mode. We should not start a new DI without checking the status of the previous DI: because the DI takes a lot of time and when we met some problems, we should analyze them before starting a new DI, otherwise, we might lose time and catch the same error. For automatic mode, we also can use Karate test and Jenkins job to start import and another Jenkins job (or the same) for analyzing the status of Job (Completed, not Completed, Completed with Errors).
- Would be good to have:
- assess to some graphical analytics tools: we need to check how much memory our modules use(s). This is also related to CPU resources and open DB connections.
- all logs should be collected in Kibana
- some tool for analyzing application metrics and traces (telemetry).
...