I always use warning to indicate something actionable for the developers. Some condition they should add to their next sprint, for example. An error is somethi

I always use warning to indicate something actionable for the developers. Some condition they should add to their next sprint, for example. An error is something actionable that needs to be responded to soon. You probably don't need to send a page, but an error is a serious condition. Stack traces are extraordinarily useful in your logs. When code breaks (and it will), you want as much information surrounding that event as possible.