Fake loggers

Made-up loggers for testing. Every value is invented.

LoggerRoleWhat it does
FAKE-01normalDeep well, slow and steady
FAKE-02normalShallow well, bigger swings
FAKE-03normalTemperature only, no level channel
FAKE-04normalHourly reporter
FAKE-05lateReadings from 02:00 to 08:00 UTC arrive at 09:00
FAKE-06spikesAbout 2% of level readings are 9999, -9999 or 0
FAKE-07batteryDies over 30 days, gets patchy, goes dark, new battery on day 32
FAKE-08silentGoes silent on days 6 and 7 of each week, no catch up

Logger links give the last 24 hours as CSV. The whole fleet is at /fleet as JSON.

Trouble Site

One problem per logger, at its own location. These are meant to break things, so a test has to choose them.

LoggerTypeWhat goes wrong
TROUBLE-01Setupexternal_id is null
TROUBLE-02Setupexternal_id is still the placeholder
TROUBLE-03Setupexternal_id has commas in it
TROUBLE-04MappingOnly in the device list on odd days
TROUBLE-05MappingUnknown channel 777 appears on odd days
TROUBLE-06MappingLevel switches from cm to m on odd days
TROUBLE-07Bad valuesAbout 10% of level readings are the text ERR
TROUBLE-08Bad valuesAbout 10% of level readings are null
TROUBLE-09APIHistory gives a 500 in about a third of minutes
TROUBLE-10APIHistory gives a 429 in about a third of minutes
TROUBLE-11APIHistory takes 65 seconds in about a fifth of minutes
TROUBLE-12APIHistory is always cut off mid JSON
TROUBLE-13APIHistory is always empty, even the units
TROUBLE-14HistoryEvery reading comes back twice
TROUBLE-15HistoryReadings come back shuffled
TROUBLE-16HistoryAlways answers with readings older than asked for
TROUBLE-17Real lifeexternal_id flips between two wells each week
TROUBLE-18Real lifeTimestamps are 6 hours in the future

Version 1.0.0. Privacy policy