[Custom threshold/Inventory] context.alertDetailsUrl is empty in Serverless

[benakansara]

The context.alertDetailsUrl is empty in alert notifications (active/recovered actions) in Serverless for Custom threshold and Inventory rules.

Below is the context of custom threshold alert notification.

"context": {
    "alertDetailsUrl": "",
    "reason": "Average system.cpu.total.norm.pct is 45.1%, above the threshold of 10%. (duration: 5 mins, data view: fake-hosts)",
    "timestamp": "2023-11-27T14:37:36.493Z",
    "value": [
      "45.1%"
    ],
    "tags": []
},

Seems to be related to not having below configuration in kibana.yml. cc @maryam-saeidi

server.basePath: "/abc"
server.publicBaseUrl: "http://localhost:5601/abc"

Update: The issue occurs only when running Serverless project locally. In Serverless QA environment, the alertDetailsUrl was correctly generated.

@maryam-saeidi Should we create relative URL like we have for viewInAppUrl when publicBaseUrl is not specified for "stateful" (as I think it will be the same case for stateful if publicBaseUrl is not specified)?

[elasticmachine]

Pinging @elastic/obs-ux-management-team (Team:obs-ux-management)

[maryam-saeidi]

@maryam-saeidi Should we create relative URL like we have for viewInAppUrl when publicBaseUrl is not specified for "stateful" (as I think it will be the same case for stateful if publicBaseUrl is not specified)?

It would be better to ensure server.publicBaseUrl is available in Serverless. The current behavior is similar to what we have for rule.url, for example, and it is mentioned in the description of the action variable as well:

This issue should not happen in the stateful cloud as we always have server.publicBaseUrl, and I see you also checked the Serverless cloud, and there was no issue. So, I think, we only need to fix not having server.publicBaseUrl locally for Serverless.

[jasonrhodes]

As this is a local only problem and we haven't addressed it yet, can we close this? @benakansara

[benakansara]

yes, let's close it