Remove Detection Rule telemetry from Security Solution (8.0+)

[pjhampton]

Summary

I have opened this pull request for discussion.

From some internal wrangling, It seems based on RAC changes that Detection Rule telemetry is bust 8.0+.
After chatting with @stevewritescode we are making the case for removing it completely for these releases - this is because we have found there was been little to no interaction with the data from 7.13 (April 2020).

Related PRs:

• @rylnd [Security Solution][Detections] Adoption telemetry #71102
• @rylnd [Security Solution][Detections] Critical: Filter out non-Detections jobs in Detections telemetry #74456
• @pjhampton [7.13][Security Solution] Fetch detection adoption metrics #97789
• @pjhampton 7.13: Fix size with detection rule telemetry. #99900
• @clburn-elastic Update detection rule telemetry field name.  #100256
• @pjhampton ES query returning no records for d-rule alerts #102160

There is a cross-team discussion as to the data we want to collect from 8.2 and index it in a way that is useful for technical and non-technical stakeholders.

For maintainers

• This was checked for breaking API changes and was labeled appropriately

[elasticmachine]

Pinging @elastic/security-solution (Team: SecuritySolution)

[pjhampton]

@elasticmachine merge upstream

[rylnd]

we have found there was been little to no interaction with the data from 7.13

@pjhampton can you expound on this a bit? Is there an expected vs. actual level of interaction?

[pjhampton]

Thanks, @rylnd. I have replied to you offline.
If you are aware of the use of this data from other teams please point me in their direction.

[pjhampton]

@elasticmachine merge upstream

[kibana-ci]

💚 Build Succeeded

• Buildkite Build
• Commit: d1bc9c9
• Storybooks Preview

Metrics [docs]

✅ unchanged

History

• 💛 Build #7957 was flaky 2f99ff3
• 💔 Build #7711 failed 59c7955
• 💔 Build #7705 failed 7b53cce

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

cc @pjhampton

[rylnd]

@pjhampton we are tracking the broken telemetry as part of https://github.com/elastic/security-team/issues/1018#issuecomment-937323352 and will have it fixed as part of 8.0. As discussed offline, we expect that the downstream ingest process will be update to make this data more usable moving forward.

[pjhampton]

@rylnd Sounds good. We have this planned on our end for 8.1 FF.
Closing. Thanks, everyone!