[ResponseOps] Add telemetry for the es query rule types

[doakalexi]

Resolves #176237

Summary

Adds new telemetry fields to track the ES Query rule search types.

Checklist

• Unit or functional tests were updated or added to match the most common scenarios

To verify

• Create a couple of ES Query rules with the different search types

• Create a rule that is not an ES Query rule

• Change alerting telemetry task schedule interval 1 min

• Run Telemetry usage payload API in your browser console to verify the telemetry data looks the same

[doakalexi]

/ci

[doakalexi]

/ci

[elasticmachine]

Pinging @elastic/response-ops (Team:ResponseOps)

[ymao1]

Would it make more sense to try to add it to the count_by_type object?

So something like:

{
  "count_by_type": {
    "__es-query": 3,
    "__es-query_es_query: 1,
    "__es-query_search_source: 1,
    "__es-query_esql_query: 1,
  }
}

Also, do we want to get the number of active (enabled) rules of these types?

[doakalexi]

Would it make more sense to try to add it to the count_by_type object?

So something like:

{
  "count_by_type": {
    "__es-query": 3,
    "__es-query_es_query: 1,
    "__es-query_search_source: 1,
    "__es-query_esql_query: 1,
  }
}

Also, do we want to get the number of active (enabled) rules of these types?

Resolved in this commit 170416c

[ymao1]

LGTM. Works as described.

[kibana-ci]

💚 Build Succeeded

• Buildkite Build
• Commit: 28d7e4c

Metrics [docs]

✅ unchanged

History

• 💔 Build #192694 failed dabcf78
• 💚 Build #192423 succeeded 8602207
• 💔 Build #192097 failed b15d076

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream