-
Notifications
You must be signed in to change notification settings - Fork 131
feat: added atlas local deployment id to telemetry #627
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
return this.executeWithAtlasLocalClient(client, ...args); | ||
} | ||
|
||
protected async lookupDeploymentIdAndAddToTelemetryMetadata(client: Client, containerId: string): Promise<void> { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit - you're not really adding it to telemetry metadata, you're just setting the deploymentId right?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This was the best name I could think of. I'm open to suggestions.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lookupDeploymentId
, setDeploymentId
, updateDeploymentId
- I think you're doing only one thing, no need for the AndAdd...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, I went with lookupDeploymentId
.
Proposed changes
Added atlas local deployment ID to telemetry.
Jira: [MCP-160] [mongodb-mcp-server] Update existing MongoDB telemetry