Skip to content

Identify CMT version in Cassandra connection metadata#52

Merged
niteshvijay1995 merged 2 commits into
mainfrom
feat/cassandra-application-name
Jul 20, 2026
Merged

Identify CMT version in Cassandra connection metadata#52
niteshvijay1995 merged 2 commits into
mainfrom
feat/cassandra-application-name

Conversation

@niteshvijay1995

@niteshvijay1995 niteshvijay1995 commented Jul 20, 2026

Copy link
Copy Markdown
Collaborator

Summary

  • set CMT as the DataStax C# driver application name
  • set 3.0.0 as the driver application version
  • apply both values centrally to every source and target cluster built by CassandraClientFactory
  • move the app version into the shared processor project so driver metadata and the UI version stay aligned

The driver receives:

.WithApplicationName("CMT")
.WithApplicationVersion(AppVersion.Value) // 3.0.0

Cosmos DB request telemetry exposes the application-name portion as Application/CMT. The application version remains available in the Cassandra STARTUP metadata even though Cosmos diagnostic userAgent_s does not currently include that separate field.

Validation

  • dotnet build CassandraMigrationWebApp/CassandraMigrationWebApp.csproj --no-restore
  • build succeeded with 0 warnings and 0 errors

Set the DataStax driver application name on the shared cluster builder so source and target requests are identifiable as CassandraMigrationTool in Cassandra and Cosmos DB telemetry.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Copilot-Session: 078ac7b9-aa7f-44a1-9053-44c346cec5e1
Copilot AI review requested due to automatic review settings July 20, 2026 04:54

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR makes Cassandra migration traffic identifiable in Cassandra/Cosmos DB request telemetry by setting a consistent DataStax C# driver application name for all sessions created via CassandraClientFactory.

Changes:

  • Introduces a single ApplicationName constant ("CassandraMigrationTool").
  • Applies the application name centrally on the base cluster Builder via .WithApplicationName(ApplicationName) so it affects both source (Cosmos DB) and target (OSS Cassandra) connections.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Use CMT as the Cassandra driver application name and 3.0.0 as its application version. Move the version constant into the shared processor project so telemetry metadata and the UI version stay aligned.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Copilot-Session: 078ac7b9-aa7f-44a1-9053-44c346cec5e1
Copilot AI review requested due to automatic review settings July 20, 2026 04:58
@niteshvijay1995 niteshvijay1995 changed the title Identify Cassandra migration connections in telemetry Identify CMT version in Cassandra connection metadata Jul 20, 2026

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Copilot reviewed 3 out of 3 changed files in this pull request and generated no new comments.

@niteshvijay1995
niteshvijay1995 merged commit 9f738b5 into main Jul 20, 2026
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants