Explanation | The accept header uses an unsupported format. |
Action | Use appropriate headers. |
Explanation | The request type is not supported. The type must be GET or OPTIONS. |
Action | Make GET or OPTIONS requests. |
Explanation | The metric does not exist. |
Action | Enter the correct metric name. |
Explanation | The registry does not exist. |
Action | Enter the correct registry name. |
Explanation | The registry is empty. |
Action | Populate the registry with metrics. |
Explanation | The application server experienced an internal error. |
Action | Gather a set of traces and open a new issue against your application server. |
Explanation | The application server experienced an internal error. |
Action | Gather a set of traces and open a new issue against your application server. |
Explanation | The underlying method for the gauge could not be resolved. This is commonly caused by accessing a metric where the application has been unloaded. |
Action | No action required. The gauge will be automatically unregistered. |
Explanation | A Metrics API error prevents normal operation. |
Action | Review the FFDC logs and exception text to identify the problem. |