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
JMX server endpoint may return "Java comment" lines like # An error report file with more information is saved as:.
In this case JMX will return an error like error: invalid character '#' looking for beginning of value.
It'd be great to handle this case properly and log this as a warning.
Ideally an integration execution instance should be able to keep fetching the rest of the requested data/queries defined.
Nice to haves
A JMX server error may report several lines. Current jmx package is limited to read just 1 line.
It'd be great to get the whole error message logged as a single entry.
Circuit breaker. Whenever several queries fail in a row (in this case we are handling "java comment" lines, but this could be extrapolated to other errors), the jmx package client (let's call it that way, although API is a set of awful global functions sharing global state) should prevent next queries to be submitted and log an error instead. This will avoid worsening the JMX endpoint scenario, as it already returned N errors in a row.
The text was updated successfully, but these errors were encountered:
Description
JMX server endpoint may return "Java comment" lines like
# An error report file with more information is saved as:
.In this case JMX will return an error like
error: invalid character '#' looking for beginning of value
.It'd be great to handle this case properly and log this as a warning.
Ideally an integration execution instance should be able to keep fetching the rest of the requested data/queries defined.
Nice to haves
A JMX server error may report several lines. Current
jmx
package is limited to read just 1 line.It'd be great to get the whole error message logged as a single entry.
Circuit breaker. Whenever several queries fail in a row (in this case we are handling "java comment" lines, but this could be extrapolated to other errors), the
jmx
package client (let's call it that way, although API is a set of awful global functions sharing global state) should prevent next queries to be submitted and log an error instead. This will avoid worsening the JMX endpoint scenario, as it already returned N errors in a row.The text was updated successfully, but these errors were encountered: