Fail the flow the when detector type is missing in the log types index

[goyamegh]

Description

Checks if the detector type is missing in the log types index and handle the edge case gracefully.

Issues Resolved

#844

Check List

• New functionality includes testing.
  • All tests pass
• New functionality has been documented.
  • New functionality has javadoc added
• Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

[codecov]

Codecov Report

Attention: 3 lines in your changes are missing coverage. Please review.

Comparison is base (0bbdb31) 24.83% compared to head (8552688) 24.82%.
Report is 4 commits behind head on main.

Files	Patch %	Lines
...yanalytics/correlation/VectorEmbeddingsEngine.java	0.00%	3 Missing ⚠️

Additional details and impacted files

@@             Coverage Diff              @@
##               main     #845      +/-   ##
============================================
- Coverage     24.83%   24.82%   -0.01%     
  Complexity     1030     1030              
============================================
  Files           277      277              
  Lines         12713    12716       +3     
  Branches       1401     1401              
============================================
  Hits           3157     3157              
- Misses         9292     9295       +3     
  Partials        264      264              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[eirsep]

Can you add more detail in description about when such edge case happens.

• why is detector type missing from log index?
• is this seen for pre-packaged log type? if yes, this might not be the right way to deal with the edge case

[goyamegh]

Can you add more detail in description about when such edge case happens.

• why is detector type missing from log index?
• is this seen for pre-packaged log type? if yes, this might not be the right way to deal with the edge case

This is not reproducible right out of the box. This exception was observed in the logs and we are adding checks and logs to understand the production use-cases here.

[eirsep]

value of detectorType is missing in in onFailures() message

[opensearch-trigger-bot]

The backport to 2.7 failed:

The process '/usr/bin/git' failed with exit code 1

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-2.7 2.7
# Navigate to the new working tree
cd .worktrees/backport-2.7
# Create a new branch
git switch --create backport/backport-845-to-2.7
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 8d19912fe1515a515b3d6a4c3f46064ab8047bb0
# Push it to GitHub
git push --set-upstream origin backport/backport-845-to-2.7
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-2.7

Then, create a pull request where the base branch is 2.7 and the compare/head branch is backport/backport-845-to-2.7.