[
https://issues.apache.org/jira/browse/METRON-1218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16185833#comment-16185833
]
ASF GitHub Bot commented on METRON-1218:
----------------------------------------
Github user simonellistonball commented on a diff in the pull request:
https://github.com/apache/metron/pull/779#discussion_r141869253
--- Diff:
metron-interface/metron-rest/src/main/java/org/apache/metron/rest/controller/RestExceptionHandler.java
---
@@ -45,4 +45,14 @@ private HttpStatus getStatus(HttpServletRequest request)
{
}
return HttpStatus.valueOf(statusCode);
}
+
+ private String getFullMessage(Throwable ex) {
+ String fullMessage = ex.getMessage();
+ Throwable cause = ex.getCause();
+ while(cause != null) {
+ fullMessage = cause.getMessage();
+ cause = cause.getCause();
+ }
+ return fullMessage;
--- End diff --
@merrimanr I'm suggesting we log it somewhere, right now there is no
apparent indication in the rest logs, so people end up hunting. When I hit the
missing alter: nested template the other day, it took a PCAP of the transport
protocol to find out what the actual root error was.
> Metron REST should return better error messages
> -----------------------------------------------
>
> Key: METRON-1218
> URL: https://issues.apache.org/jira/browse/METRON-1218
> Project: Metron
> Issue Type: Bug
> Reporter: Ryan Merriman
> Assignee: Ryan Merriman
>
> Currently, Metron REST does not provide enough detail when an error happens.
> For example, an error that happens in the search endpoint will simply return
> "Could not execute search" with no detail and nothing in the metron-rest.log.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
