/stylesheets/landing.css 404

[andrew-pickin-epi]

See (if it's not expired) https://kibana-hmlr.epimorphics.net/app/kibana#/discover/doc/6c14b5b0-14b7-11ec-a649-5d4fa077ce2c/fluentd-20211013?id=VZCHeXwBbnGrmRJQlMTI&_g=()

key	value
log_path	/stylesheets/landing.css
log_referrer	http://hmlr-dev-pres.epimorphics.net/search?et%5B%5D=lrcommon%3Afreehold&et%5B%5D=lrcommon%3Aleasehold&limit=1000&nb%5B%5D=true&nb%5B%5D=false&paon=Bristol&ptype%5B%5D=lrcommon%3Adetached&ptype%5B%5D=lrcommon%3Asemi-detached&ptype%5B%5D=lrcommon%3Aterraced&ptype%5B%5D=lrcommon%3Aflat-maisonette&ptype%5B%5D=lrcommon%3AotherPropertyType&tc%5B%5D=ppd%3AstandardPricePaidTransaction&tc%5B%5D=ppd%3AadditionalPricePaidTransaction
log_request_id	YWbKk4dg29jhda2Kb4G9KgAAAAc
log_status	404

[andrew-pickin-epi]

Further there is nothing that report or alerts this as an error.

[ijdickinson]

Unclear to me what the ask is here. From what I can tell, a client app had a reference to an out-of-date landing.css stylesheet. When the apps are updated, old versions that are cached in browsers might end up with stale references, which 404 when the user interacts with the app. The stale ref should clear when the user refreshes the page.

Further there is nothing that report or alerts this as an error.

I'm not sure if you're saying that it alert and it shouldn't (because it's just a 404), or that it didn't alert and it should have (which I'm not sure I agree with, since there's nothing we can do about stale cached copies of the app)

[andrew-pickin-epi]

Ok, if this is a stale deployment then so be it but I though this was a new deployment I'm not sure how anything stale got deployed here.

[andrew-pickin-epi]

{"level":"ERROR","ts":"2021-11-02T16:04:57.269Z","request_id":"YYFhqXEOYaxosIUsj1N-JAAAAAw","message":"ActionController::RoutingError (No route matches [GET] "/stylesheets/landing.css"):","rails":{"environment":"production"}}

Ok I've just recreated. Doesn't thins indicate that the current deployment of the landing image has reference to a non-existent css file?
Even if this isn't the case but one of those things "that just might happen" then it's not a ERROR.

[ijdickinson]

Ok I've just recreated. Doesn't thins indicate that the current deployment of the landing image has reference to a non-existent css file?

It does look that way (or, at least, it's the wrong path to a file that does exist). @bogdanadrianmarc Can you please investigate.

Even if this isn't the case but one of those things "that just might happen" then it's not a ERROR.

I agree. I thought we had added something to json_rails_logger to change the level if it was reporting a 404. Again, one for Bogdan to look at.

[mika018]

https://github.com/epimorphics/hmlr-ansible-deployment/issues/72