Skip to content

Commit 4a4d90d

Browse files
authored
APPSEC-60188: downgrade integration response parsing log to debug (#959)
The message was incorrectly kept as `warn!` when we donwgraded all these log messages to `debug!` and this is very noisy in customer accounts. JJ-Change-Id: zkowts ZD: 2375557 Jira: APPSEC-60188
1 parent ea48140 commit 4a4d90d

File tree

1 file changed

+2
-2
lines changed
  • bottlecap/src/appsec/processor

1 file changed

+2
-2
lines changed

bottlecap/src/appsec/processor/mod.rs

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ use libdd_trace_protobuf::pb::Span;
1313
use libddwaf::object::{WafMap, WafOwned};
1414
use libddwaf::{Builder, Config as WafConfig, Handle};
1515
use tokio::sync::Mutex;
16-
use tracing::{debug, info, warn};
16+
use tracing::{debug, info};
1717

1818
use crate::appsec::processor::context::Context;
1919
use crate::appsec::processor::response::ExpectedResponseFormat;
@@ -131,7 +131,7 @@ impl Processor {
131131
ctx.run(payload.as_ref());
132132
}
133133
Ok(None) => debug!("aap: no response payload available"),
134-
Err(e) => warn!("aap: failed to parse invocation result payload: {e}"),
134+
Err(e) => debug!("aap: failed to parse invocation result payload: {e}"),
135135
}
136136

137137
let (method, route, status_code) = ctx.endpoint_info();

0 commit comments

Comments
 (0)