Home

Awesome

Iowa Environmental Mesonet

If using this code causes your server to have kittens, it is your own fault.

This monolith drives much of the ingest, processing, product generation, and web presence of the IEM. Hopefully it can be found useful for others to at least look at to see how some of the magic happens.

Limited integration testing is done on Github Actions: Build Status DeepSource codecov

Database schema is in akrherz/iem-database.

Where are processes running

The processing load for the IEM is spread over a number of virtual machines. This is an attempt to document what is running where. The backup shown may not be automated, but another system that could be up and running the service in limited time.

ProcessPrimaryBackupMonitor
GOES R/Siem8-dciem19None
hrrriem8-dcNoneNone
iembotiem11-dcNonenagios
iemdb1metvm33-dciemvm4nagios check
iemdb2metvm4-dciemvm5nagios check
iemdb3metvm2-dciemvm0nagios check
iem-archivemetvm6-dciemvm6nagios
iem-web-servicesiem27-dciem11-dcnagios check
letsencrpytiem8-dcNonenagios SSL check
LDMiem11NoneNone
LoggerNetiem8-dcNonenagios check
memcachedmetvm0-dciem8-dcnagios check
NEXRAD Mosaicsiem8-dciem16nagios checks archive
NWWS-OI Ingestiem12NoneNone
openfireiem11-dcNoneNone
rabbitmqiem9-dciem8-dcnagios check
sambaiem16Nonecron scripts check data availability
RIDGEiem9-dcNoneinbound file queue, check latency 7 radars
webalizeriem8-dcNoneNone
webcam haproxyiem19iem12nagios
Webcam Currentiem19Nonecron script monitors for offline webcams
Webcam Lapsesiem19NoneNone