[Logs UI] Support inline log views in http routes

[weltenwort]

📓 Summary

Currently the HTTP routes used by the browser to fetch log data require a sourceId parameter which is used to look up the LogView for the request. In order to allow for querying log data based on inline log views, the HTTP routes must be able to also accept full log view definitions as a parameter so step of loading it from a saved object can be skipped.

✔️ Acceptance criteria

• All log-related HTTP routes in the infra plugin (except for the log view routes themselves), that take a sourceId parameter instead take a logView parameter as described below.
• The logView parameter can contain either...
  • a log view reference by id as already defined in

    kibana/x-pack/plugins/infra/common/log_views/types.ts

    Lines 106 to 111 in e5895c3

    	export const logViewReferenceRT = rt.type({
    	logViewId: rt.string,
    	type: rt.literal('log-view-reference'),
    	});
    	export type LogViewReference = rt.TypeOf<typeof logViewReferenceRT>;

    or
  • an inline log view like { type: 'inline-log-view', id: string, attributes: logViewAttributesRT }
• The routes handle requests referring to a log-view-reference like before with the sourceId by loading and resolving the log view.
• The routes handle requests referring to an inline-log-view by resolving the given attributes with LogViewClient.resolveLogView() directly.

💡 Implementation hints

• The log-view-reference type is already defined in

  kibana/x-pack/plugins/infra/common/log_views/types.ts

  Lines 106 to 111 in e5895c3

  	export const logViewReferenceRT = rt.type({
  	logViewId: rt.string,
  	type: rt.literal('log-view-reference'),
  	});
  	export type LogViewReference = rt.TypeOf<typeof logViewReferenceRT>;

  . It just needs to be wrapped in a union together with the new inline-log-view type.

[elasticmachine]

Pinging @elastic/infra-monitoring-ui (Team:Infra Monitoring UI)