-
Notifications
You must be signed in to change notification settings - Fork 104
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix fieldLimit exception in docLevelMonitor #1368
Changes from 1 commit
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -87,8 +87,16 @@ object DocumentLevelMonitorRunner : MonitorRunner() { | |
monitorCtx.alertIndices!!.createOrUpdateInitialFindingHistoryIndex(monitor.dataSources) | ||
} catch (e: Exception) { | ||
val id = if (monitor.id.trim().isEmpty()) "_na_" else monitor.id | ||
logger.error("Error setting up alerts and findings indices for monitor: $id", e) | ||
monitorResult = monitorResult.copy(error = AlertingException.wrap(e)) | ||
val unwrappedException = ExceptionsHelper.unwrapCause(e) as Exception | ||
if (unwrappedException is IllegalArgumentException && unwrappedException.message?.contains("Limit of total fields") == true) { | ||
val errorMessage = | ||
"Monitor [$id] can't process index [$monitor.dataSources] due to field mapping limit" | ||
logger.error(errorMessage) | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. we can pass a custom message to user but can we log the original exception here instead? |
||
monitorResult = monitorResult.copy(error = AlertingException(errorMessage, RestStatus.INTERNAL_SERVER_ERROR, e)) | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. A 4XX (maybe 400) would be more appropriate here than a 500 imo since the field limit getting hit is from user behavior rather than an internal server error |
||
} else { | ||
logger.error("Error setting up alerts and findings indices for monitor: $id", e) | ||
monitorResult = monitorResult.copy(error = AlertingException.wrap(e)) | ||
} | ||
} | ||
|
||
try { | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
if you unwrap and cast to generic Exception how will this check
unwrappedException is IllegalArgumentException
be true ever?