Question

Azure Monitor

  • 16 May 2023
  • 3 replies
  • 87 views

Badge +3

 

Hi,

 

While trying to connect Centreon to Azure Monitor I’m getting below error. Can someone please guide on what needs to be done to resolve it.

 
Status information

UNKNOWN: Management endpoint API returns code 'BadRequest'

Message : ApiVersion: 2018-01-01 does not support query at non Arm resource Id level

 


3 replies

Userlevel 4
Badge +12

Hi @mmnawab,

Can you give us a little more information?

For example the command you are trying to run ? Without password/user secret/any confidential data of course.

Badge +3

 

I'm running command "Cloud-Azure-Management-Monitor-Api-Get-Metrics" betting below status


Status information
UNKNOWN: Management endpoint API returns code 'BadRequest' (add --debug option for detailed message)

== Info: Trying 51.107.60.33...

== Info: TCP_NODELAY set

== Info: Connected to management.azure.com (51.107.60.33) port 443 (#0)

== Info: ALPN, offering http/1.1

== Info: successfully set certificate verify locations:

== Info: CAfile: /etc/pki/tls/certs/ca-bundle.crt

CApath: none

== Info: TLSv1.3 (OUT), TLS handshake, Client hello (1):

== Info: TLSv1.3 (IN), TLS handshake, Server hello (2):

== Info: TLSv1.2 (IN), TLS handshake, Certificate (11):

== Info: TLSv1.2 (IN), TLS handshake, Server key exchange (12):

== Info: TLSv1.2 (IN), TLS handshake, Server finished (14):

== Info: TLSv1.2 (OUT), TLS handshake, Client key exchange (16):

== Info: TLSv1.2 (OUT), TLS change cipher, Change cipher spec (1):

== Info: TLSv1.2 (OUT), TLS handshake, Finished (20):

== Info: TLSv1.2 (IN), TLS handshake, Finished (20):

== Info: SSL connection using TLSv1.2 / ECDHE-RSA-AES256-GCM-SHA384

== Info: ALPN, server accepted to use http/1.1

== Info: Server certificate:

== Info: subject: C=US; ST=WA; L=Redmond; O=Microsoft Corporation; CN=management.azure.com

== Info: start date: Mar 20 17:24:28 2023 GMT

== Info: expire date: Mar 14 17:24:28 2024 GMT

== Info: subjectAltName: host "management.azure.com" matched cert's "management.azure.com"

== Info: issuer: C=US; O=Microsoft Corporation; CN=Microsoft Azure TLS Issuing CA 06

== Info: SSL certificate verify ok.

=> Send header: GET XXXX

Host: management.azure.com

Authorization:Bearer XXXX

Accept:application/json

=> Recv header: HTTP/1.1 400 Bad Request

=> Recv header: Cache-Control: no-cache

=> Recv header: Pragma: no-cache

=> Recv header: Content-Length: 108

=> Recv header: Content-Type: application/json; charset=utf-8

=> Recv header: Expires: -1

=> Recv header: x-ms-correlation-request-id: XXXX

=> Recv header: x-ms-ratelimit-remaining-subscription-reads: 11992

=> Recv header: Request-Context: appId=cid-v1:XXXX

=> Recv header: x-ms-request-id: {XXXX}

=> Recv header: Strict-Transport-Security: max-age=31536000; includeSubDomains

=> Recv header: Access-Control-Allow-Origin: *

=> Recv header: x-ms-routing-request-id: SWITZERLANDNORTH:XXXX

=> Recv header: X-Content-Type-Options: nosniff

=> Recv header: Date: Tue, 16 May 2023 07:03:06 GMT

=> Recv header:

=> Recv data: {"code":"BadRequest","message":"ApiVersion: 2018-01-01 does not support query at non Arm resource Id level"}

== Info: Connection #0 to host management.azure.com left intact

Message : ApiVersion: 2018-01-01 does not support query at non Arm resource Id level

 

Badge +3

Appreciate it if someone could please share some insight on how to get this fixed. Thanks.

Reply