-
Notifications
You must be signed in to change notification settings - Fork 110
Description
Hi,
We have been exploring the MuleSoft Metrics Toolkit available on GitHub - https://github.com/mulesoft-catalyst/metrics-toolkit/tree/main. While retrieving the platform metrics request data, we observed that some of the values, particularly under runtimeManagerMetrics.cloudhub, appear incorrectly calculated.
We would like to highlight the discrepancies in the following fields:
vcoresAvailable
vcoresUsed
applicationsStarted
applicationsStopped
For example, in both Production and Sandbox environments, the values for vcoresUsed, applicationsStarted, and applicationsStopped are showing as zero, despite active deployments.
Sample from the response:
"production": {
"vcoresTotal": 25,
"vcoresAvailable": 25,
"vcoresUsed": 0,
"applicationsTotal": 0,
"applicationsStarted": 0,
"applicationsStopped": 0,
"runtimesUsed": []
},
"sandbox": {
"vcoresTotal": 18,
"vcoresAvailable": 18,
"vcoresUsed": 0,
"applicationsTotal": 0,
"applicationsStarted": 0,
"applicationsStopped": 0,
"runtimesUsed": []
}
We have attached the full JSON response file for your reference.
Additionally, we tried publishing custom metrics using Anypoint Monitoring's Custom Metrics Loader. While the data is published successfully (As we don't get any error), we are unable to view it under Anypoint Platform → Monitoring → Built-In Dashboards → Custom Metrics. We’ve attached relevant screenshots showing the issue.
We would appreciate your help in:
Validating the discrepancies observed in the metrics fields mentioned above.
Understanding the expected behavior and prerequisites for viewing published custom metrics on the Anypoint Platform dashboard.
Looking forward to your support on this.