@byscott-io/where-is-waldo 0.1.9 → 0.1.10
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +8 -0
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -113,6 +113,14 @@ WhereIsWaldo.configure do |config|
|
|
|
113
113
|
config.timeout = 90 # seconds until offline
|
|
114
114
|
config.heartbeat_interval = 30
|
|
115
115
|
|
|
116
|
+
# Observability: when true (default) and the host app runs a supported APM
|
|
117
|
+
# agent (New Relic today), presence heartbeats are kept out of APM as their
|
|
118
|
+
# own transactions. Heartbeats are the highest-volume, least-interesting cable
|
|
119
|
+
# action, so reporting each one inflates throughput and flatters average
|
|
120
|
+
# response time without adding signal. Failures are still reported. Set false
|
|
121
|
+
# to report heartbeats like any other action.
|
|
122
|
+
config.ignore_heartbeat_apm = true
|
|
123
|
+
|
|
116
124
|
# Optional: custom subject data in presence hash. NOTE: with the roster
|
|
117
125
|
# enabled, these fields are broadcast to every member of the org — see
|
|
118
126
|
# Security.
|