| | 36 | |
| | 37 | == timezones == |
| | 38 | * I agreed to change the timestamps in incident filenames (which exist so you |
| | 39 | can glance at a list of them and pick out the one that happened at around |
| | 40 | the same time you did something weird or noticed a problem) to report UTC |
| | 41 | instead of the local timezone where the process is running. This annoys me |
| | 42 | because I don't know what current UTC time is, so when I'm looking at a |
| | 43 | local server (or one that's been configured to pretend it's in the same |
| | 44 | timezone as I am), I can't compare the incident filenames against my |
| | 45 | personal time. This trades off value for people looking at filenames from |
| | 46 | remote timezones against value for locals: UTC is equally bad for |
| | 47 | everybody. (#111). The three basic choices are: |
| | 48 | 1: localtime (which is ambiguous) |
| | 49 | 2: localtime+TZ (i.e. append -0800 for PST), which is verbose |
| | 50 | 3: UTC+Z, which can't be compared against my watch or my memory |
