Done
Details
Assignee
UnassignedUnassignedReporter
Andrii SkomorokhovAndrii Skomorokhov(Deactivated)Priority
HighNeeds QA
YesNeeds Doc
YesFix versions
Story Points
3Sprint
None
Details
Details
Assignee
Unassigned
UnassignedReporter
Andrii Skomorokhov
Andrii Skomorokhov(Deactivated)Priority
Needs QA
Yes
Needs Doc
Yes
Fix versions
Story Points
3
Sprint
None
Smart Checklist
Smart Checklist
Smart Checklist
Created March 10, 2021 at 4:34 PM
Updated March 6, 2024 at 3:03 AM
Resolved April 2, 2021 at 2:54 PM
User story:
When I need to add Azure related DB for the monitoring I need to be able to enter Azure related credentials in PMM UI (add Instance) So I can see the list of all DB existed in the Azure account and processed with Adding them to PMM for monitoring
UI/UX:
TBD
something related to :
Acceptance criteria
User can enter credentials: AZURE_CLIENT_ID, AZURE_CLIENT_SECRET, AZURE_TENANT_ID, AZURE_SUBSCRIPTION_ID click discovery and see the list of DB services possible monitor by PMM
List of DBs should contain: Name, DomainName, resourceGroup, Type, Version, Location (port is unavailable - check if standard port works)
The user is able to select a DB from the list and proceed to a screen to fill more details to start to monitor it by PMM.
On the screen of Add remote MySQL (PostgreSQL/MariaDB) Instance, the user can see and edit the next fields (filled in or empty):
DomainName - filled in
Service Name - default DomainName
Port - default for DB type: 3306, 5432 - check if it works - ports does not return with selected resource discovery
user - filled in by concatenating "<administratorLogin>@<name>"
Password - empty
Labels
Region - repopulated by location
Environment - filled in by tags.environment
Do we need fill in any other labels?
Custom labels empty
Additional option - need additional investigation
User able to do all operations using Azure and PMM UI only
The Discovery process works for:
Azure Database for PostgreSQL
Azure Database for MySQL
Azure Database for MariaDB - need an additional investigation - as it stays separate from "standard" Azure DB - and its cost does not encourage to do many experiments.
Here is a screenshot of adding Azure Monitor as a datasource
Also Resource group is required.
It's not clear if it has to be discovered automatically or added as new instance each time with whole list of *ids.
Out of scope:
any Azure SQL related discovery
Suggested implementation:
TBD
Risks:
Discovery and monitoring of MariaDB
How to form DSN
TLS
**
How to test:
Create DB on Azure
Genarates credentials.
Discover from grafana
Add to monitor
See matrics on garafana dashboard.
More detailed TBD
TBD
Details: