Skip to content
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

Azure database exporter not working #3095

Open
1 task done
ctradar opened this issue Jul 25, 2024 · 3 comments
Open
1 task done

Azure database exporter not working #3095

ctradar opened this issue Jul 25, 2024 · 3 comments
Assignees
Labels
bug Bug report

Comments

@ctradar
Copy link

ctradar commented Jul 25, 2024

Description

Azure database exporter not working. Followed this guide

Expected Results

Fetch metrics from Azure successfully

Actual Results

Failing with error 4xx

Version

2.38.0 (tried with version 2.30.0 and latest version 2.42.0 as well)

Steps to reproduce

Enable Azure Monitoring technical preview feature. Add managed database service and enable Azure metrics checkbox while doing so.

Relevant logs

ERRO[2024-07-25T05:47:11.939+00:00] time="2024-07-25T05:47:11Z" level=error msg="Received 400 status for resource /subscriptions/redacted/resourceGroups/redacted/providers/Microsoft.DBforPostgreSQL/flexibleServers/redacted3/providers/microsoft.insights/metrics?aggregation=Average&api-version=2018-01-01&metricnames=cpu_percent%2Cmemory_percent%2Cstorage_percent%2Cstorage_used%2Cstorage_limit%2Cnetwork_bytes_egress%2Cnetwork_bytes_ingress&timespan=2024-07-25T05%3A43%3A11Z%2F2024-07-25T05%3A44%3A11Z. " source="main.go:58"  agentID=/agent_id/f90f739c-c0de-4966-b626-7c0dadf4ab35 component=agent-process type=azure_database_exporter

Code of Conduct

  • I agree to follow Percona Community Code of Conduct
@ctradar ctradar added the bug Bug report label Jul 25, 2024
@ctradar
Copy link
Author

ctradar commented Jul 25, 2024

@Nailya
Copy link

Nailya commented Jul 31, 2024

@ctradar i couldn't reproduce this issue. Could you check if the database is running and all credentials are correct?

@nkprince007
Copy link

Yes, the database was indeed running and using correct azure service principal credentials.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Bug report
Projects
None yet
Development

No branches or pull requests

4 participants