aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorTyler Davis <tyler@gluecode.net>2024-12-11 18:18:01 +0000
committerTyler Davis <tyler@gluecode.net>2024-12-11 18:18:01 +0000
commit509fe00d541ce769c4423a072318ad47294b7763 (patch)
tree8936d699e1e42a06df97655dc67e912edd023f05
parent04429378bbf9fb1d2858041473a91e402e181b49 (diff)
downloadstandards-509fe00d541ce769c4423a072318ad47294b7763.tar.gz
standards-509fe00d541ce769c4423a072318ad47294b7763.zip
Finish the sentence
-rw-r--r--docs/monitoring.md3
1 files changed, 2 insertions, 1 deletions
diff --git a/docs/monitoring.md b/docs/monitoring.md
index d9a9b62..d868672 100644
--- a/docs/monitoring.md
+++ b/docs/monitoring.md
@@ -36,7 +36,8 @@ For the purposes of monitoring and alerting, the following definitions apply:
- **Event**: a record of something which happened, produced by a Monitor.
- A monitoring _event_ is not the same as events used in other systems such as Databases, Cloud Providers, Apache Kafka, etc.
- Events are records, not signals, and MUST represent something that actually happened.
- Such occurrences represent decisions made by the
+ Such occurrences represent decisions made by the Development, SRE, and
+ Security teams to highlight _meaningful_ occurrences.
## Types of Monitoring