okta: Add benchmarks

[kcreddy]

Add following benchmarks as part of improving integration quality:

• Pipeline benchmarks
• Rally benchmarks
• System benchmarks

[elasticmachine]

Pinging @elastic/security-service-integrations (Team:Security-Service Integrations)

[github-actions]

TL;DR: Okta currently has no benchmark scaffolding, so I recommend implementing this in two milestones (pipeline+rally, then system) using the same structure already used by recent integrations; this is actionable now and consistent with repo precedent.

Recommendation

Implement benchmarks for packages/okta by following existing package conventions: add pipeline benchmark assets under the system data stream first, then add package-level rally and system benchmark suites. A split rollout (PR1 pipeline+rally, PR2 system) reduces risk and matches how benchmark work has been shipped in similar integrations when system benchmarking needed extra setup.

Findings

• Issue scope is explicit (pipeline, rally, system): #17994.
• Okta package exists and has one stream (system):
  • packages/okta/data_stream/system/manifest.yml:1-4
• Okta has pipeline tests, but no benchmark directory:
  • packages/okta/data_stream/system/_dev/test/pipeline/test-okta-system-events.log-config.yml:1-10
  • verification command returned okta_pipeline_benchmark_dir_exit=1
• Benchmark command support is documented in-repo:
  • docs/extend/elastic-package.md:52-60
• Canonical benchmark examples (pipeline + rally + system + deploy):
  • packages/trend_micro_vision_one/data_stream/alert/_dev/benchmark/pipeline/config.yml:1
  • packages/trend_micro_vision_one/_dev/benchmark/rally/alert-benchmark.yml:1-15
  • packages/trend_micro_vision_one/_dev/benchmark/system/alert-benchmark.yml:1-24
  • packages/trend_micro_vision_one/_dev/benchmark/system/deploy/docker/docker-compose.yml:1-16
• Related completed issues indicate this work is standard for integration quality:
  • #17393, #17071, #14741.

Verification

I ran the following checks locally:

$ cd /home/runner/work/integrations/integrations
$ test -d packages/okta/data_stream/system/_dev/benchmark/pipeline; echo "okta_pipeline_benchmark_dir_exit=$?"
okta_pipeline_benchmark_dir_exit=1

$ find packages/*/data_stream/*/_dev/benchmark/pipeline/config.yml | wc -l
35

$ cd packages/okta
$ go run github.com/elastic/elastic-package benchmark pipeline --help | head -n 12
Run pipeline benchmarks for the package
Usage:
  elastic-package benchmark pipeline [flags]
...

Interpretation: benchmark command path is available, but Okta is missing required benchmark files/directories.

Detailed Action Plan

1. Add pipeline benchmark assets for Okta system stream:

   • packages/okta/data_stream/system/_dev/benchmark/pipeline/config.yml
   • packages/okta/data_stream/system/_dev/benchmark/pipeline/system-sample.log (or .json corpus)

2. Add rally benchmark suite at package level:

   • packages/okta/_dev/benchmark/rally/system-benchmark.yml
   • packages/okta/_dev/benchmark/rally/system-benchmark/{template.ndjson,config.yml,fields.yml}

3. Add system benchmark suite + deploy harness:

   • packages/okta/_dev/benchmark/system/system-benchmark.yml
   • packages/okta/_dev/benchmark/system/system-benchmark/{template.ndjson,config.yml,fields.yml}
   • packages/okta/_dev/benchmark/system/deploy/docker/docker-compose.yml
   • packages/okta/_dev/benchmark/system/deploy/docker/files/config.yml

4. Validate in package context (cd packages/okta):

   • go run github.com/elastic/elastic-package benchmark pipeline --data-streams system -v
   • go run github.com/elastic/elastic-package benchmark rally -v (if enabled in your environment)
   • go run github.com/elastic/elastic-package benchmark system -v (with deploy config)

5. If system benchmark introduces environment-specific complexity, keep it as PR2 and close checklist items incrementally in this issue.

Related Items

Type	Link	Relevance
Issue	#17994	Current request
Issue	#17393	Similar benchmark request completed
Issue	#17071	Similar benchmark request completed
Issue	#14741	Similar benchmark request, phased completion
PR	#17563	Example adding pipeline+rally+system benchmarks
PR	#17067	Example system benchmark follow-up
File	packages/okta/data_stream/system/manifest.yml	Okta stream target
File	packages/trend_micro_vision_one/_dev/benchmark/system/deploy/docker/docker-compose.yml	System benchmark deploy pattern

---

What is this? | From workflow: Issue Triage

Give us feedback! React with 🚀 if perfect, 👍 if helpful, 👎 if not.