Fireaxe enabled, watching /ls/yudfwra/production/fireaxe/SIGNED/yudfwra/cloud-ml-vertex-genai-dataplane-staging-jobs/staging-qual-us.vertex-genai-dataplane.
Active Emergency Actions
No active emergency actions.
To add an emergency action for this job, run a command like:
/google/bin/releases/fireaxe-cli/fireaxe block_client <client_user_name_here> \ /bns/yudfwra/borg/yudfwra/bns/cloud-ml-vertex-genai-dataplane-staging-jobs/staging-qual-us.vertex-genai-dataplane
See go/fireaxe-user-guide for documentation about different actions.
Inspect all actions in Automon
You can find the raw metrics under /production/fireaxe/ Streamz
Effective Stubby Server Limits
Fireaxe uses the native RPC server actions implementation, and does not control the RateACL config. See /rateaclz for the effective RateACL config and running stats of allowed and denied RPCs.
No per-client connection count limits generated by Fireaxe. See /rpcz/server2 for static connection count limits configured through flags.
RPC Interceptors (Request / Response Filtering)
Incoming RPCs from clients: Fireaxe interceptor installed in the RPC server. No filters.
Outgoing RPCs to backends: Fireaxe interceptor installed in the RPC client. No filters.
Configuration
rpc_acl_config_source:
FIREAXE
Fireaxe is enabled, CDD is disabled. RateACL uses Fireaxe only, LabelACL uses flags and environment variables, connection count limits use flags and Fireaxe.
fireaxe_realm:
PROD
Process Identity:
/bns/yudfwra/borg/yudfwra/bns/cloud-ml-vertex-genai-dataplane-staging-jobs/staging-qual-us.vertex-genai-dataplane/1
Full config file proto:
[empty]