Default Cosmos Db Metrics in Azure Monitor

%3CLINGO-SUB%20id%3D%22lingo-sub-2204830%22%20slang%3D%22en-US%22%3EDefault%20Cosmos%20Db%20Metrics%20in%20Azure%20Monitor%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2204830%22%20slang%3D%22en-US%22%3E%3CP%3EI%20was%20trying%20to%20configure%20the%20default%20cosmos%20db%20metrics%20on%20azure%20monitor%20to%20get%20requests%2C%20throughputs%2C%20and%20other%20related%20info.%20as%20given%20in%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fazure-monitor%2Finsights%2Fcosmosdb-insights-overview%23overview%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%22%3Edocumentation.%3C%2FA%3E%3CBR%20%2F%3EOne%20issue%20I%20found%20was%20that%20if%20I%20have%20a%20collection%20by%20the%20name%20of%20%22test%22%20in%20my%20database%20in%20cosmos%20db%20account%20%2C%20I%20sometimes%20see%20two%20collections%20in%20Azure%20monitor%20under%20my%20database%20that%20are%20%22Test%22%20and%20%22test%22.But%20this%20is%20kind%20of%20intermittent%20and%20if%20I%20change%20the%20time%20range%20it%20sometimes%20start%20showing%20one%20collection%20only.%20I%20have%20checked%20there%20is%20no%20collection%20by%20the%20name%20of%20%22Test%22%20(with%20capital%20T)%20in%20my%20database.%3CBR%20%2F%3EAnd%20also%20the%20results%20provided%20are%20actually%20distributed%20within%20the%20two%20metrics.%3CBR%20%2F%3ESo%2C%20what%20can%20be%20the%20reason%20for%20this%20behaviour%20%3F%3CBR%20%2F%3E(I%20have%20attached%20a%20screenshot%20for%20the%20same.)%3C%2FP%3E%3CP%3E%3CBR%20%2F%3EAlso%20one%20suggestion%20in%20Monitor%20metrics%2C%20all%20the%20collections%20are%20segregated%20at%20the%20account%20not%20at%20the%20database%20level.%20If%20we%20have%20different%20databases%20in%20an%20account%20with%20the%20same%20collection%20name%20how%20can%20metrics%20tell%20which%20collection%20in%20database%20got%20how%20many%20requests%20as%20it%20gives%20a%20single%20collection%20name%20for%20all%20the%20databases%20%3F%20Shouldn't%20this%20be%20at%20the%20database%20level%20%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E
Regular Visitor

I was trying to configure the default cosmos db metrics on azure monitor to get requests, throughputs, and other related info. as given in documentation.
One issue I found was that if I have a collection by the name of "test" in my database in cosmos db account , I sometimes see two collections in Azure monitor under my database that are "Test" and "test".But this is kind of intermittent and if I change the time range it sometimes start showing one collection only. I have checked there is no collection by the name of "Test" (with capital T) in my database.
And also the results provided are actually distributed within the two metrics.
So, what can be the reason for this behaviour ?
(I have attached a screenshot for the same.)


Also one suggestion in Monitor metrics, all the collections are segregated at the account not at the database level. If we have different databases in an account with the same collection name how can metrics tell which collection in database got how many requests as it gives a single collection name for all the databases ? Shouldn't this be at the database level ?

0 Replies