-
Type:
Bug
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
Atlas Streams
-
ALL
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Invalid database names in a pipeline are currently being classified as internal errors instead of user errors:
{ [-]
_p: F
authDB: admin
caller: v1/server.go:242
clientHostname: mhouse-frontend-66bbd977d5-bxgt5
clientServiceAccount: mhouse-frontend
commandName: StartStreamProcessor
connectionID: 406689198
correlationID: 183200c9b1b043498ab1c882
dataLakeType: STREAM
endpoint: /com.xgen.mhouse.services.streamprocessormanager.grpc.v1.ManagerService/StartStreamProcessor
error: $merge to Project 0.notifications failed: Invalid database name: 'Project 0': generic server error
errorCode: 73
gitVersion: d69a4c5416b8109c9ebca315da1737789991c9fd
hostname: atlas-stream-67eac1e4f40a543f33dfb9a4-eqd2i.virginia-usa.z.query.mongodb.net
internalTimestamp: 2025-03-31T21:34:44.276Z
isInternal: true
kube: { [-]
container_name: streams-spm
labels: { [-]
xgen_app: streams-spm
xgen_environment: prod
xgen_kube_cluster: kube-1-eastus2-azure-cloud
xgen_provider: azure
xgen_region: eastus2
xgen_version: d69a4c5416b8109c9ebca315da1737789991c9fd
}
namespace: streams-prod
node: aks-streams2-32904639-vmss0000lh
pod_name: streams-spm-6ccf57b4db-ffnfm
}
level: info
logger: stream-processor-manager
msg: streams command failure
projectID: 67a67e9e835cad3ae909b897
remoteIP: 10.32.70.196
stream: stdout
streamProcessorID: 67eb0a6407e37b0cc0d1286e
streamProcessorName: notificationsStreamProcessor
tenantID: 67eac1e4f40a543f33dfb9a4
time: 2025-03-31T21:34:44.276401893Z
username: isaiah-dev
x-request-id: 183200c9b1b043498ab1c882
}