Synthetic monitoring response inconsistent - a

Aspose.Words Cloud Product Family
1

As per my previous discussion : Aspose on premise approach giving red message boxes in converted pdf - #26 by yaroslaw.ekimov

We were advised to put a regular check on api with endpoint ‘<base_url> + /v4.0/words/info’
and to keep a check on key ‘IsMeteredLicensed’ if true or not.
For example :

{
“Name”: “Aspose.Words Cloud API”,
“Version”: “24.12.0”,
“AdditionalInfo”: [
{
“Key”: “ConsumptionCredit”,
“Value”: “57744”
},
{
“Key”: “ConsumptionQuantity”,
“Value”: “23667.3795”
},
{
“Key”: “IsMeteredLicensed”,
“Value”: “True”
}
],
“RequestId”: “a519cfcc-a92a-4534-ad47-0730232db191”
}

Since yesterday, intermittently the additionalInfo array seem to be missing:

{
  "Name": "Aspose.Words Cloud API",
  "Version": "24.12.0",
  "RequestId": "01d14233-3837-4321-96a7-724d4a7b96b7"
}

Please check asap as there is already an issue with redmark for on premise approach and we were finally able to do this work around. Api response needs to be consistent

2

@rajatdpw

It seems you are experiencing inconsistencies with the API response when checking the endpoint for the Aspose.Words Cloud API. Specifically, the AdditionalInfo array, which should include keys like ConsumptionCredit, ConsumptionQuantity, and IsMeteredLicensed, is intermittently missing from the response.

This inconsistency can be problematic, especially since you rely on this information for monitoring purposes. Here are a few steps you can take to address this issue:

  1. Check API Status: Ensure that there are no ongoing issues with the Aspose API services. Sometimes, temporary outages or maintenance can affect the response structure.

  2. Implement Error Handling: Modify your monitoring script to handle cases where the AdditionalInfo array is missing. This could involve logging the occurrence and possibly retrying the request after a short delay.

  3. Contact Support: Since this issue seems to be affecting your workflow significantly, consider reaching out to Aspose support directly. Provide them with the details of the inconsistency, including timestamps and any patterns you’ve noticed.

  4. Review Documentation: Keep an eye on the official Aspose documentation or forums for any updates regarding changes to the API response structure.

If you have further questions or need assistance with specific code implementations, feel free to ask!

3

Please consider this on priority.

4

If you didn’t change image, it may be the reason why you get watermark with register message, I will contact the billing team to check logs may be this behavior gives them more information.

5

We are using 24.12

This should be fine, right?

6

Yes, it is okay. I meant that maybe they could find out why it stopped returning IsMetered

1 Like
7

yeah like as you can see above, complete additionalInfo array is missing. Please confirm with this and may be also checking if we can avoid this issue from your end also.