Expose overall status to plugins (elastic#75503)

Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>

docs/development/core/server/kibana-plugin-core-server.statusservicesetup.md

@@ -17,4 +17,5 @@ export interface StatusServiceSetup
 |  Property | Type | Description |
 |  --- | --- | --- |
 |  [core$](./kibana-plugin-core-server.statusservicesetup.core_.md) | <code>Observable&lt;CoreStatus&gt;</code> | Current status for all Core services. |
+|  [overall$](./kibana-plugin-core-server.statusservicesetup.overall_.md) | <code>Observable&lt;ServiceStatus&gt;</code> | Overall system status for all of Kibana. |
 

docs/development/core/server/kibana-plugin-core-server.statusservicesetup.overall_.md

@@ -0,0 +1,20 @@
+<!-- Do not edit this file. It is automatically generated by API Documenter. -->
+
+[Home](./index.md) &gt; [kibana-plugin-core-server](./kibana-plugin-core-server.md) &gt; [StatusServiceSetup](./kibana-plugin-core-server.statusservicesetup.md) &gt; [overall$](./kibana-plugin-core-server.statusservicesetup.overall_.md)
+
+## StatusServiceSetup.overall$ property
+
+Overall system status for all of Kibana.
+
+<b>Signature:</b>
+
+```typescript
+overall$: Observable<ServiceStatus>;
+```
+
+## Remarks
+
+The level of the overall status will reflect the most severe status of any core service or plugin.
+
+Exposed only for reporting purposes to outside systems and should not be used by plugins. Instead, plugins should only depend on the statuses of [Core](./kibana-plugin-core-server.statusservicesetup.core_.md) or their dependencies.
+

src/core/server/legacy/legacy_service.ts

@@ -322,6 +322,7 @@ export class LegacyService implements CoreService {
       },
       status: {
         core$: setupDeps.core.status.core$,
+        overall$: setupDeps.core.status.overall$,
       },
       uiSettings: {
         register: setupDeps.core.uiSettings.register,

src/core/server/plugins/plugin_context.ts

@@ -178,6 +178,7 @@ export function createPluginSetupContext<TPlugin, TPluginDependencies>(
     },
     status: {
       core$: deps.status.core$,
+      overall$: deps.status.overall$,
     },
     uiSettings: {
       register: deps.uiSettings.register,

src/core/server/server.api.md

@@ -2802,6 +2802,7 @@ export type StartServicesAccessor<TPluginsStart extends object = object, TStart
 // @public
 export interface StatusServiceSetup {
     core$: Observable<CoreStatus>;
+    overall$: Observable<ServiceStatus>;
 }
 
 // @public

src/core/server/status/status_service.mock.ts

@@ -39,6 +39,7 @@ const availableCoreStatus: CoreStatus = {
 const createSetupContractMock = () => {
   const setupContract: jest.Mocked<StatusServiceSetup> = {
     core$: new BehaviorSubject(availableCoreStatus),
+    overall$: new BehaviorSubject(available),
   };
 
   return setupContract;

src/core/server/status/types.ts

@@ -123,13 +123,20 @@ export interface StatusServiceSetup {
    * Current status for all Core services.
    */
   core$: Observable<CoreStatus>;
-}
 
-/** @internal */
-export interface InternalStatusServiceSetup extends StatusServiceSetup {
   /**
-   * Overall system status used for HTTP API
+   * Overall system status for all of Kibana.
+   *
+   * @remarks
+   * The level of the overall status will reflect the most severe status of any core service or plugin.
+   *
+   * Exposed only for reporting purposes to outside systems and should not be used by plugins. Instead, plugins should
+   * only depend on the statuses of {@link StatusServiceSetup.core$ | Core} or their dependencies.
    */
   overall$: Observable<ServiceStatus>;
+}
+
+/** @internal */
+export interface InternalStatusServiceSetup extends StatusServiceSetup {
   isStatusPageAnonymous: () => boolean;
 }