How can we separately monitor two databases in a single Azure Cache for Redis Instance?
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 20/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- azure, redis
- Domain
- cloud, observability
Research direction
Start with the Azure Monitor Docs and the Azure Monitor website, focusing on Azure Cache for Redis metrics and the 16 logical databases within an instance. Determine whether monitoring can be separated by logical database and whether per-database resource usage is exposed; document the supported monitoring scope and any limitation found.
Written by the indexing model from the issue text.
Description
I have gone through the Azure Monitor Docs and also played around on their website, but what I have only found out is that we can monitor a particular resource, i.e. if I create a Azure Cache for Redis instance that I can only monitor what happens in that instance, but since one instance has the capability of creating 16 different logical databases, is it possible to separately monitor those databases accordingly, and find out if how much resource is each of the database using in that single redis instance?
- Dominant language
- PowerShell
- Stars
- 1.2k
- Forks
- 493
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from microsoft/AzureMonitorCommunity
-
Difficulty 3/5 1-2 days Newbie friendliness 58/100
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
-
Difficulty 4/5 3-5 days Newbie friendliness 10/100
All issues in microsoft/AzureMonitorCommunity
Similar issues
-
Language: Terraform :globe_with_meridians: Needs: Triage :mag: Type: Bug :bug:
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Azure/terraform-azurerm-avm-res-containerregistry-registry#230 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
level/task module/gcp type/bug
Difficulty 2/5 1-3 hours Newbie friendliness 85/100