don't send pagerduty alerts for websocket panics

TODO.md

@@ -319,6 +319,8 @@ These are not yet ordered. There might be duplicates. We might not actually need
   - this will let us easily wait for a new head or a new synced connection
 - [x] broadcast transactions to more servers
 - [x] send sentryd errors to pagerduty
+- [x] improve handling of unknown methods
+- [x] don't send pagerduty alerts for websocket panics
 - [-] proxy mode for benchmarking all backends
 - [-] proxy mode for sending to multiple backends
 - [-] let users choose a % of reverts to log (or maybe x/second). someone like curve logging all reverts will be a BIG database very quickly

web3_proxy/src/bin/web3_proxy_cli/main.rs

@@ -231,6 +231,9 @@ fn main() -> anyhow::Result<()> {
             let hostname = gethostname().into_string().unwrap_or("unknown".to_string());
             let panic_msg = format!("{} {:?}", x, x);
 
+            if panic_msg.starts_with("panicked at 'WS Server panic") {
+                info!("Underlying library {}", panic_msg);
+            } else {
                 error!("sending panic to pagerduty: {}", panic_msg);
 
                 let payload = AlertTriggerPayload {
@@ -256,6 +259,7 @@ fn main() -> anyhow::Result<()> {
                 if let Err(err) = pagerduty_sync.event(event) {
                     error!("Failed sending panic to pagerduty: {}", err);
                 }
+            }
         }));
     }