You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
this depends on adding "index-alerts-history" which won't happen now.
once we have that, we can run:
POST /_sql?format=json
{
"query": """
SELECT
providerId AS alert_provider_id,
providerType AS alert_provider_type,
DATE_FORMAT(lastReceived, 'yyyy-MM-dd HH') AS "time",
COUNT(*) AS hits,
MAX(lastReceived) AS last_alert_timestamp
FROM
"keep-alerts-%tenant-id%"
WHERE
lastReceived >= NOW() - INTERVAL 1 DAY
GROUP BY
providerId,
providerType,
DATE_FORMAT(lastReceived, 'yyyy-MM-dd HH')
ORDER BY
providerId,
providerType,
DATE_FORMAT(lastReceived, 'yyyy-MM-dd HH')
"""
}
shahargl
changed the title
[Bug]: provider distribution should use search engine (elastic)
[enhancement]: provider distribution should use search engine (elastic)
Jul 4, 2024
talboren
changed the title
[enhancement]: provider distribution should use search engine (elastic)
[🔨 Enhancement]: provider distribution should use search engine (elastic)
Jul 8, 2024
Describe the bug
When deploying Keep with elastic, it still calc provider distribution on the database
The text was updated successfully, but these errors were encountered: