Should we keep the prefill logic in the custom threshold rule?

[maryam-saeidi]

📝 Summary

While working on using searchConfiguration.query instead of query field, I noticed that we have some logic to set the query based on the metadata. Bena pointed out that this logic is used in the Metric threshold to prefill the component based on the Metric Explorer view information as shown below: (used in AlertFlyout)

Now the question is, do we need to keep this logic for the custom threshold?
If no, we need to remove this extra logic.
If yes, we need to see where this logic will be used, considering we also need to select the right data view.

✅ Acceptance Criteria

• Discuss the usage of prefill logic with @katrin-freihofner and in case it is not needed, clean up the extra code from observability plugin.

[elasticmachine]

Pinging @elastic/actionable-observability (Team: Actionable Observability)

[maryam-saeidi]

After a brief talk with Katrin, she said:
We will no longer use this logic to pre-fill information in the Metric Explorer view, but we want a similar functionality from the new Host view. About which field we want to prefill, we need to check this with the Infra team and @roshan-elastic

[maryam-saeidi]

This logic is covered in #170295