Core usage data

[rudolf]

Summary

Core Telemetry Service for supplying core metrics to a usage collector (usage collector not implemented yet). I aimed to collect the easy metrics to get this in before FF, but this doesn't collect all the metrics we identified in #56762

Checklist

Delete any items that are not applicable to this PR.

• Any text added follows EUI's writing guidelines, uses sentence case text and includes i18n support
• Documentation was added for features that require explanation or tutorials
• Unit or functional tests were updated or added to match the most common scenarios
• This was checked for keyboard-only and screenreader accessibility
• This renders correctly on smaller devices using a responsive layout. (You can test this in your browser
• This was checked for cross-browser compatibility

For maintainers

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

[TinaHeiligers]

@rudolf If it's not too late, can we please rename from "telemetry" to "usage data"? We're trying really hard to reserve using "Telemetry" for only sending the data to the service. We already have a telemetry plugin that it responsible for sending the data and don't want to get the terminology mixed up. It makes it really difficult to debug SDH issues. 🙏

[elasticmachine]

Pinging @elastic/kibana-platform (Team:Platform)

[rudolf]

Still blocked on worked around the issue

node scripts/telemetry_check.js --fix
 ✔ Checking .telemetryrc.json files
 ❯ Extracting Collectors
   ✖ Extracting collectors in /Users/rudolf/dev/kibana/src/plugins/
     → TypeError: Cannot read property 'resolvedFileName' of undefined
     Extracting collectors in /Users/rudolf/dev/kibana/x-pack/plugins/
   Checking Compatible collector.schema with collector.fetch type
   Generating new telemetry mappings
   Updating telemetry mapping files
ERROR Unhandled exception!
ERROR Error: Error extracting collector in src/plugins/kibana_usage_collection/server/collectors/core/core_usage_collector.ts
      TypeError: Cannot read property 'resolvedFileName' of undefined
          at createFailError (/Users/rudolf/dev/kibana/packages/kbn-dev-utils/target/run/fail.js:26:26)
          at parseUsageCollection (/Users/rudolf/dev/kibana/packages/kbn-telemetry-tools/src/tools/ts_parser.ts:205:17)
          at parseUsageCollection.next (<anonymous>)
          at extractCollectors (/Users/rudolf/dev/kibana/packages/kbn-telemetry-tools/src/tools/extract_collectors.ts:73:12)
          at extractCollectors.next (<anonymous>)
          at Task.task (/Users/rudolf/dev/kibana/packages/kbn-telemetry-tools/src/tools/tasks/extract_collectors_task.ts:54:36)

[rudolf]

Because the telemetry team asked us not to use ...Telemetry I've switched to ...UsageData but CoreUsageData['usageData'] is a bit awkward, so I deviated from the "spec" in the original issue by using the key "services" with the idea that we would group usage data under the respective Core services they originate from e.g. savedObjects / plugins.

[afharo]

It looks great! Just added a couple of NITs.

Reading through your PR, I acknowledge we (the telemetry team) need to work on our documentation 😅

[joshdover]

LGTM. Tested with localhost:5601/api/stats?extended and it seemed to work correctly 😄. A couple small nits is all.

[kibanamachine]

💚 Build Succeeded

• continuous-integration/kibana-ci/pull-request
• Commit: afe0114

Metrics [docs]

distributable file count

id	before	after	diff
default	44119	44125	+6
oss	28595	28601	+6

History

• 💔 Build #79445 failed 062280e
• 💔 Build #79165 failed 65954a6
• 💔 Build #79123 failed 4de37e2
• 💔 Build #79061 failed dbee8f9
• 💔 Build #79055 failed a508a0a

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