Skip to main content

Reports section shows a file that doesn't exist hogging all of the stats

Devin Gibson

I have 5 images that get called upon fairly evenly, but there is one file getting all of the stats and it's not a file or image that exists. This non-existent file is getting 75 requests while the other existing images are getting 1 - 5. So it's like it's stealing the stats from the images.

Has anyone run into this before?

0

Comments

4 comments

Date Votes
  • Tia Esguerra

    Hi Devin. 

    I can see that the URL is being requested, and our error reports show that the HTTP status code 400 is being returned. This means that the URL is invalid. However, this URL exists somewhere in your application or website, so the requests are being made by your site's visitors. On the 16th of December, this URL was requested 45 times from local host http://127.0.0.1:58661/ 
    I am only able to see that these requests are being made. I cannot see where they are coming from. So I would advise you to track down which page is making the request and then you can fix that URL. 

    I hope this helps. Let me know if there is anything further I can do to help. 

    Kind Regards, 

    Tia

    1
  • Devin Gibson

    That helps quite a bit, thank you! :D

    I have a js file that calls up the images from cloudinary sequentially, and the url changes to increase the count each time. It looks like

    "url(https://res.cloudinary.com/givr/image/upload/v1637975768/" + coupons[count] + ")"

    I do end up getting the right images delivered, but maybe the way it comes together messes up the stats? Is there a way to turn off stat recording for assets that don't exist?

    0
  • Devin Gibson

    It looks like I can generate stats for anything as long as I put it into the URL. This feels like a bug with Cloudinary reporting to me. I can force stats for files like bug.png, secretmessage.jpg, and anything else I want.

    0
  • Eric Pasos

    Hi Devin,

    As the number of requests and bandwidth usages is based on all the requests logs including the failed ones, this is the current behavior of the Media Library Reports page. Also, the report page is mainly used to show top usage/consumption and since there are only a few transactions currently available in your account, those failed requests data are included in the display as well. And, the filtering mechanism to exclude those failed requests data is currently unavailable.

    Hope this helps.

    0

Post is closed for comments.

Didn't find what you were looking for?

New post