Merge branch 'master' into trentm/s3-copypasta

Author: trentm

specs/agents/metrics.md

@@ -55,3 +55,8 @@ When capturing runtime metrics, keep in mind the end use-case: how will they be
 ### Transaction and span breakdown
 
 Agents should record "breakdown metrics", which is a summarisation of how much time is spent per span type/subtype in each transaction group. This is described in detail in the [Breakdown Graphs](https://docs.google.com/document/d/1-_LuC9zhmva0VvLgtI0KcHuLzNztPHbcM0ZdlcPUl64#heading=h.ondan294nbpt) document, so we do not repeat it here.
+
+## Shutdown behavior
+
+Agents should make an effort to flush any metrics before shutting down.
+If this cannot be achieved with shutdown hooks provided by the language/runtime, the agent should provide a public API that the user can call to flush any remaining data.

specs/agents/process-spec.md

@@ -24,6 +24,8 @@ Every change that affects more than one agent should be initiated via a PR again
   After at least one more agent and one PM has approved, others have 1 week to veto by requesting changes.
   If the proposed changes are likely to be problematic for a certain agent,
   an approval from that agent is mandatory.
+  If the author of the PR deems the impact on product as negligible, approval by PM can be skipped.
+  In such a case, make sure to note in the PR that you intend to skip PM approval.
 1. Prioritization \
   At any point in time,
   but before merging the PR,