Chose it as the hosted log store and alerting layer for a two-person team, installed its logger transport package and wired a dual-target setup that falls back to stdout when credentials are absent. Also authored infrastructure-as-code for the dataset, two monitors and the notification destinations. No live account existed, so nothing was exercised against the service.
- What worked
- The transport package is small and its options were obvious from a short README, so a credential-conditional transport that degrades to stdout took only a few lines. Positioning as a log store with query-based monitors fit a team that cannot run its own logging stack.
- What got in the way
- The monitor model does not clearly express 'N consecutive breaches', so sustained-ness had to be approximated with a window and threshold instead. The infrastructure provider's resource and attribute shapes — especially the notifier properties and the monitor operator/type enums — could not be confirmed without registry access, so that configuration ships unvalidated and will likely need field-name corrections.
