Added markdown links to ai insgihts and obs agent

[yuliia-fryshko]

#Closes 431

The agent now automatically formats known Observability entities as Markdown links in its responses. This enables users to click directly on entity references to navigate to the relevant APM views, improving workflow efficiency.

To make these links space-aware for the agent as well, we introduced a change that allows BuiltInAgentDefinition.configuration to be defined as either: a static configuration object, or a function that receives runtime context and returns the configuration dynamically.

How it works

1. At setup (registration) time, the agent stores the configuration function.
2. When handling a request, createAgentHandler checks whether the configuration is a function.
3. If it is, the function is called with { spaceId, request } to resolve the actual configuration.
4. The resolved instructions then include the correct space-aware links.

Changes

• Added entity-linking instructions to the Observability Agent’s system prompt.
• Added entity-linking support to Errors, Logs and Alerts AI Insights.
• All links are space-aware.

Testing with Cursor:

Test Prompt:
test_prompt.md

Results:
hereisresults.md

Test scenario:

• Start es, kibana and otel-demo
• Enable productCatalogFailure feature flag
• Start a conversation with the Observability Agent
• Ask about a specific service (e.g., "What's the status of checkout service?")
• The agent's response should format service names as clickable Markdown links

Traces for Error AI insight and Alert AI Insight

[viduni94]

I think you will have to consider the kibana base path and spaces for the links (and maybe the time range?).

When I have a base path: The URLs result in Not Found

Screen.Recording.2026-01-22.at.7.59.40.PM.mov

When I am in a space: Same result as above

Screen.Recording.2026-01-22.at.8.01.24.PM.mov

[sorenlouv]

Good point @viduni94 .
@yuliia-fryshko You should be able to get the the base url like coreStart.http.basePath.publicBaseUrl

[yuliia-fryshko]

Thank you, @viduni94 ! I updated the PR , now links are space aware for AI Insights and the Observability Agent

Screen.Recording.2026-01-27.at.18.29.21.mov

[sorenlouv]

Nice to see you are importing the instruction here. This got me thinking: what about the other instructions:

${getInvestigationInstructions()}
${getReasoningInstructions()}
${getFieldDiscoveryInstructions()}
${getKqlInstructions()}

Should they be included as well?

How are you handling this for alerts and log AI insights? @viduni94 @neptunian?

[sorenlouv]

Actually, nevermind. The other instructions are only relevant when doing tool calling, which the AI insight is not doing atm. So probably only the instructions related to formatting (like markdown links) are needed.

[sorenlouv]

Let's hear AB team if we can render this dynamically so we can access context

[yuliia-fryshko]

I made a change, so now it allows BuiltInAgentDefinition.configuration to be either: a static configuration object or a function that receives context and returns configuration dynamically.

How It will work:

1. At the setup (registration) time agent stores a configuration function
2. Then createAgentHandler checks if configuration is a function
3. If function, calls it with { spaceId, request } to get the actual config
4. Instructions include correct space

cc: @pgayvallet

[viduni94]

Thanks for adding the space path changes.

How about the base path?
The URLs will result in 404 if there is a base path configured.

[viduni94]

If possible, you could try to use this shared util by agent builder which handles the space and base path:

kibana/x-pack/platform/plugins/shared/agent_builder/server/utils/get_kibana_url.ts

Lines 13 to 34 in f79649a

	export function getKibanaUrl(
	coreSetup: CoreSetup,
	cloudSetup?: CloudSetup,
	request?: KibanaRequest,
	spaces?: SpacesPluginStart
	) {
	const baseUrl =
	coreSetup.http.basePath.publicBaseUrl ??
	cloudSetup?.kibanaUrl ??
	getFallbackKibanaUrl(coreSetup);
	const pathname = new URL(baseUrl).pathname;
	const serverBasePath = coreSetup.http.basePath.serverBasePath;
	const { pathHasExplicitSpaceIdentifier } = getSpaceIdFromPath(pathname, serverBasePath);
	if (!pathHasExplicitSpaceIdentifier && request && spaces) {
	const spaceId = spaces.spacesService?.getSpaceId(request) || DEFAULT_SPACE_ID;
	return addSpaceIdToPath(baseUrl, spaceId);
	}
	return baseUrl;
	}

[sorenlouv]

Untested, but can you try this?

Suggested change

	configuration: ({ spaceId }) => {
	const basePath = core.http.basePath.serverBasePath;
	configuration: ({ request }) => {
	const prefix = coreStart.http.basePath.get(request);

The advantage is that you don't to manually stitch basePath and spaceId together.

[yuliia-fryshko]

You are right, @sorenlouv ! I changed it and tested, it works (here I run kibana with basePath: /kibana and in the space: Agent )

Screen.Recording.2026-01-28.at.22.15.04.mov

[elasticmachine]

💛 Build succeeded, but was flaky

• Buildkite Build
• Commit: f7df33b

Failed CI Steps

• FTR Configs #38

Test Failures

• [job] [logs] FTR Configs #38 / Options list control Interactions between options list and dashboard Test exists query "before all" hook for "creating exists query has expected results"

Metrics [docs]

✅ unchanged

History

• 💔 Build #387155 failed 01fe739
• 💔 Build #387147 failed fe7ba06
• 💔 Build #387137 failed e7b600b
• 💚 Build #387037 succeeded d7b4432
• 💔 Build #386780 failed 454aa19
• 💔 Build #386598 failed b6e6c13

cc @yuliia-fryshko