[Alerting] Track deprecated configs

[chrisronline]

Resolves #112585
Replaces #112609

This adds usage telemetry for:

• xpack.actions.whitelistedHosts
• xpack.actions.customHostSettings.ssl.rejectUnauthorized
• xpack.actions.rejectUnauthorized
• xpack.actions.proxyRejectUnauthorizedCertificates
• xpack.alerts.healthCheck
• xpack.alerts.invalidateApiKeysTask.interval
• xpack.alerts.invalidateApiKeysTask.removalDelay
• xpack.task_manager.max_workers

To test, add these configs to your kibana.yml and hit the stats HTTP API (https://localhost:5601/api/stats?extended). You should see some data in kibana_config_usage and some in deprecated_keys

{
  "deprecated_keys": {
    "unset": [
      "xpack.actions.whitelistedHosts",
      "xpack.actions.customHostSettings.ssl.rejectUnauthorized",
      "xpack.actions.rejectUnauthorized",
      "xpack.actions.proxyRejectUnauthorizedCertificates",
      "xpack.alerts.healthCheck",
      "xpack.alerts.invalidateApiKeysTask.interval",
      "xpack.alerts.invalidateApiKeysTask.removalDelay"
    ]
  }
}

{
  "kibana_config_usage": {
    "xpack_task_manager_max_workers": 120,
  }
}

(kibana.yml for the above)

xpack.actions.whitelistedHosts: ['smtp.gmail.com']
xpack.actions.allowedHosts: ['smtp.gmail.com']
xpack.actions.rejectUnauthorized: true
xpack.actions.proxyRejectUnauthorizedCertificates: true
xpack.alerting.healthCheck.interval: 60m
xpack.alerts.healthCheck.interval: 120m
xpack.alerts.invalidateApiKeysTask.interval: 5m
xpack.alerts.invalidateApiKeysTask.removalDelay: 2h
xpack.task_manager.max_workers: 120

[elasticmachine]

Pinging @elastic/kibana-alerting-services (Team:Alerting Services)

[chrisronline]

@elasticmachine merge upstream

[ymao1]

This is unrelated to this PR but maybe a quick fix in this PR?

I had this setting in my config:

xpack.actions.customHostSettings:
  - url: smtp://smtp.gmail.com
    ssl:
      rejectUnauthorized: false
      certificateAuthoritiesFiles: '/Users/ymao/Code/kibana/packages/kbn-dev-utils/certs/ca.crt'
      certificateAuthoritiesData: |
          -----BEGIN CERTIFICATE-----
          ... multiple lines of certificate data here ...
          -----END CERTIFICATE-----
    smtp:
      requireTLS: true

and I noticed I was not getting a deprecation warning for rejectUnauthorized and not seeing the unset for the deprecated value. It looks like the logic checking for rejectUnauthorized does not evaluate correctly if rejectUnauthorized: false. Should I open a new issue to fix or do you think we can include in this PR?

[ymao1]

Same thing for xpack.actions.rejectUnauthorized and xpack.actions.proxyRejectUnauthorizedCertificates when they are set to false...the deprecation warning does not get logged.

[chrisronline]

@ymao1 Nice catch, I'll fix those in this PR

[chrisronline]

@ymao1 I made those changes, ready for another pass!

[ymao1]

LGTM!

[chrisronline]

@elasticmachine merge upstream

[chrisronline]

@elasticmachine merge upstream

[YulNaumenko]

LGTM

[kibanamachine]

💚 Build Succeeded

• continuous-integration/kibana-ci/pull-request
• Commit: 30d550a
• Storybooks Preview

Metrics [docs]

✅ unchanged

History

• 💔 Build #158440 failed 701ad73
• 💔 Build #158161 failed 7568e1d
• 💔 Build #157205 failed d8ecbc2
• 💔 Build #157120 failed ff65777
• 💛 Build #156446 was flaky 292f63a

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

cc @chrisronline