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
Sep 5 13:20:20 graylogsrv-001 systemd-entrypoint: uncaught exception in thread [DefaultDispatcher-worker-5]
Sep 5 13:20:20 graylogsrv-001 systemd-entrypoint: AlertingException[analyzer [analyzer_keyword] has not been configured in mappings]; nested: Exception[java.lang.IllegalArgumentException: analyzer [analyzer_keyword] has not been configured in mappings];
Sep 5 13:20:20 graylogsrv-001 systemd-entrypoint: at org.opensearch.alerting.util.AlertingException$Companion.wrap(AlertingException.kt:70)
Sep 5 13:20:20 graylogsrv-001 systemd-entrypoint: at org.opensearch.alerting.util.DocLevelMonitorQueries.updateQueryIndexMappings(DocLevelMonitorQueries.kt:367)
Sep 5 13:20:20 graylogsrv-001 systemd-entrypoint: at org.opensearch.alerting.util.DocLevelMonitorQueries.access$updateQueryIndexMappings(DocLevelMonitorQueries.kt:45)
Sep 5 13:20:20 graylogsrv-001 systemd-entrypoint: at org.opensearch.alerting.util.DocLevelMonitorQueries$updateQueryIndexMappings$1.invokeSuspend(DocLevelMonitorQueries.kt)
Sep 5 13:20:20 graylogsrv-001 systemd-entrypoint: at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33)
Sep 5 13:20:20 graylogsrv-001 systemd-entrypoint: at kotlinx.coroutines.DispatchedTask.run(Dispatched.kt:285)
Sep 5 13:20:20 graylogsrv-001 systemd-entrypoint: at kotlinx.coroutines.scheduling.CoroutineScheduler.runSafely(CoroutineScheduler.kt:594)
Sep 5 13:20:20 graylogsrv-001 systemd-entrypoint: at kotlinx.coroutines.scheduling.CoroutineScheduler.access$runSafely(CoroutineScheduler.kt:60)
Sep 5 13:20:20 graylogsrv-001 systemd-entrypoint: at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.run(CoroutineScheduler.kt:742)
Sep 5 13:20:20 graylogsrv-001 systemd-entrypoint: Suppressed: AlertingException[analyzer [analyzer_keyword] has not been configured in mappings]; nested: Exception[java.lang.IllegalArgumentException: analyzer [analyzer_keyword] has not been configured in mappings];
Sep 5 13:20:20 graylogsrv-001 systemd-entrypoint: ... 9 more
Sep 5 13:20:20 graylogsrv-001 systemd-entrypoint: Caused by: java.lang.Exception: java.lang.IllegalArgumentException: analyzer [analyzer_keyword] has not been configured in mappings
Sep 5 13:20:20 graylogsrv-001 systemd-entrypoint: ... 9 more
How can one reproduce the bug?
Go to Alerting>Monitors>Create monitor
Select 'Per document monitor', select any index and choose a query
Go to Preview query and performance and wait..
Try to save the monitor
What is the expected behavior?
I don't know, hence it never worked for me.
What is your host/environment?
OS: Centos7
Opensearch Version: 2.9.0
Opensearch-Dashboards Version: 2.9.0
NOTE
We are ingesting the logs using graylog.
I already opened an issue at the opensearch-project/alerting repository 3 months ago (when v2.7.0 was latest), but so far the issue hasn't been fixed.
The text was updated successfully, but these errors were encountered:
What is the bug?
When defining a new monitor (under alerting) and selecting the type 'Per document monitor', the monitor saves with following error:
Index settings:
Index mapping:
How can one reproduce the bug?
What is the expected behavior?
I don't know, hence it never worked for me.
What is your host/environment?
OS: Centos7
Opensearch Version: 2.9.0
Opensearch-Dashboards Version: 2.9.0
NOTE
The text was updated successfully, but these errors were encountered: