Where to find the central log from all services:
http://dokuwiki.picalike.corpex-kunden.de/read_the_central_log

Monitor to check for stalled feed data:
http://dokuwiki.picalike.corpex-kunden.de/lilly_monitor

Look exports:
http://dokuwiki.picalike.corpex-kunden.de/look_export

v3 mongo uris are in the swiss army knive git if something needs to be checked

v3 shop overview: http://frontend03-hpc.picalike.corpex-kunden.de:3001/

a listing of currently running feed imports can be seen on index03 (chech history for feedUpdateList.py)
→ the start dates should not be older than 2 days for more than one shop
→ the list should not be longer than 20 entries except for the morning where this sometimes happens
Witt shops feed updates are automatically triggered via fs_action on frontend01 (compare ~/bin/ and ~/etc/)

in general checking the history on index03 helps for restarting imports

atelier goldner schnitt triggered regularly

madeleine triggered regularly

modehaus triggered regularly via script on frontend01:~/modehaus

shops currently in the alerting:

2220 - sheego - no regular updates
3532 - ags ch - unclear why - needs to be fixed after holidays
7028 - eckerle - needs to be fixed by customer
8837 - witt fr - no regular updates as already mentioned

“heartbeat_monitor.py on sg01 says: LillySyncService:<HOST> is down” → if its a local host ok, but not if host is any corpex or netcup maschine (then check incidents page). (http://sg01.picalike.corpex-kunden.de:5002/by_service)

“krawla qa service failed for …” - ignore

Keywords: v3 lilly debug feed enrichment