fix: Lower log level for some span deduper logs

Author: lym953

bottlecap/src/traces/span_dedup_service.rs

@@ -3,7 +3,7 @@
 
 use tokio::sync::{mpsc, oneshot};
 use tokio::time::Duration;
-use tracing::warn;
+use tracing::info;
 
 use crate::traces::span_dedup::{DedupKey, Deduper};
 
@@ -95,7 +95,9 @@ impl DedupService {
                 DedupCommand::CheckAndAdd(key, response_tx) => {
                     let was_added = self.deduper.check_and_add(key);
                     if let Err(e) = response_tx.send(was_added) {
-                        warn!("Failed to send check_and_add response: {e:?}");
+                        // Not using warn or error level to avoid confusion for customers.
+                        // No action is needed on customer side.
+                        info!("Failed to send check_and_add response: {e:?}");
                     }
                 }
             }

bottlecap/src/traces/trace_agent.rs

@@ -19,7 +19,7 @@ use tokio::sync::{
 };
 use tokio_util::sync::CancellationToken;
 use tower_http::limit::RequestBodyLimitLayer;
-use tracing::{debug, error, warn};
+use tracing::{debug, error, info, warn};
 
 use crate::traces::trace_processor::SendingTraceProcessor;
 use crate::{
@@ -557,7 +557,9 @@ impl TraceAgent {
                         should_keep
                     }
                     Err(e) => {
-                        warn!("Failed to check span in deduper, keeping span: {e}");
+                        // Not using warn or error level to avoid confusion for customers.
+                        // No action is needed on customer side.
+                        info!("Failed to check span in deduper, keeping span: {e}");
                         true
                     }
                 };