Monitoring Azure resources with Zabbix
Comments  
Kingsley
0 # zabbix monitor from on-prem to cloudKingsley 2018-08-07 17:56
Is it possible to monitor azure resources (i.e server VMs) from on premises zabbix server
Reply | Reply with quote | Quote
Super User
0 # RE: zabbix monitor from on-prem to cloudSuper User 2018-08-10 16:25
Quoting Kingsley:
Is it possible to monitor azure resources (i.e server VMs) from on premises zabbix server


Hi!

Yep, it's possible, there is no any difference.
Reply | Reply with quote | Quote
JoseM
0 # Add Virtual MachineJoseM 2020-06-25 18:30
HI, how can i configure virtual machine monitor?
Reply | Reply with quote | Quote
Super User
0 # RE: Add Virtual MachineSuper User 2020-06-26 10:39
Quoting JoseM:
HI, how can i configure virtual machine monitor?


Hi!

I've updated code on GitHub. Working for me.
Reply | Reply with quote | Quote
JoseM
0 # Zabbix Sender problemJoseM 2020-06-26 17:13
Hi thanks for your response, i have problems with zabbix sender,
zabbix_sender -z localhost -i imports/Azure_2020-06-26T14-49-08Z.imports -T -vv
zabbix_sender [34459]: Warning: [line 1] invalid 'Timestamp' value detected
Sending failed.

The script has that line, but report that error, i did it manually and the same, what timestamp is reporting the problem?
Reply | Reply with quote | Quote
Super User
0 # RE: Zabbix Sender problemSuper User 2020-06-29 11:20
Quoting JoseM:
Hi thanks for your response, i have problems with zabbix sender,
zabbix_sender -z localhost -i imports/Azure_2020-06-26T14-49-08Z.imports -T -vv
zabbix_sender [34459]: Warning: [line 1] invalid 'Timestamp' value detected
Sending failed.

The script has that line, but report that error, i did it manually and the same, what timestamp is reporting the problem?


Hi!

Saw that as well - fixed with this:
github.com/vicioussn/zabbix-azure/commit/675422002a06cf0b7a35ffa880f1622c6f5054c7#diff-937bce56bfde53feca9ca33ef7783efbR128
Reply | Reply with quote | Quote
JoseM
0 # RE: Zabbix Sender problemJoseM 2020-06-29 17:22
Quoting Super User:


Hi, i replace the " in the script but the problem persist.

Also the template is reporting me that discovery rule is enabled but keep creating items and report the item key as already exists, it's trying to create them multiple times.

I'm working on zabbix sender error so i can move to template error, as soon i have fixed those i let you know.
Reply | Reply with quote | Quote
Super User
0 # RE: Zabbix Sender problemSuper User 2020-06-30 10:23
Quoting JoseM:

Hi, i replace the " in the script but the problem persist.

Also the template is reporting me that discovery rule is enabled but keep creating items and report the item key as already exists, it's trying to create them multiple times.

I'm working on zabbix sender error so i can move to template error, as soon i have fixed those i let you know.


Can you please put first two lines from 'imports' file?

For template reporting duplicate items - remove already created items and re-run discovery couple of times.
Reply | Reply with quote | Quote
JoseM
0 # RE: Zabbix Sender problemJoseM 2020-07-01 16:24
Quoting Super User:

Can you please put first two lines from 'imports' file?

For template reporting duplicate items - remove already created items and re-run discovery couple of times.

HI i solved those incovenients.

Now the scripts are turning unstables, sometimes work and sometimes doesn't. i'm getting this error:

VERBOSE: Item 64/84
VERBOSE: Parsing item key 'azure.resource[PFSENSE-DEMO,virtualMachines,CPU Credits Consumed,PT1M,Average]' and getting variables to make REST request.
VERBOSE: Getting time span for item 'CPU Credits Consumed - PFSENSE-DEMO' (id=86754) to determine period to pull metrics from Azure.
VERBOSE: Getting Zabbix history for item '86754'.
VERBOSE: Successfully fetched Zabbix history for item '86754'. VERBOSE: Item 'CPU Credits Consumed - PFSENSE-DEMO' (id=86754) has no values (possibly new item?). VERBOSE: Timespan = '2020-06-28T14:10:44Z - 2020-07-01T14:07:44Z'. VERBOSE: Logging to Azure.
VERBOSE: Azure Monitor API header built.
VERBOSE: Getting metric values from Azure Monitor with parameters:
VERBOSE: - resourceName = 'PFSENSE-DEMO'
VERBOSE: - resourceType = 'virtualMachines'
VERBOSE: - subscriptionId = 'ece9a1a6-d2d7-4284-b2fd-865d967c7024'
VERBOSE: - resourceGroupName = 'FISA-TEST';
VERBOSE: - timeSpan = '2020-06-28T14:10:44Z - 2020-07-01T14:07:44Z'
VERBOSE: - timeGrain = 'PT1M'
VERBOSE: - metricName = 'CPU Credits Consumed'
VERBOSE: Building URI to pull metrics from Azure Monitor.
VERBOSE: URI: management.azure.com/subscriptions/ece9a1a6-d2d7-4284-b2fd-865d967c7024/resourceGroups/FISA-TEST/providers/Microsoft.Compute/virtualMachines/PFSENSE-DEMO/providers/microsoft.insights/metrics?timespan=2020-06-28T14:10:44Z/2020-07-01T14:07:44Z&interval=PT1M&api-version=2018-01-01&metricnames=CPU Credits Consumed&aggregation=Average
VERBOSE: Error while making REST request to Azure API.
VERBOSE: Retrying 1/5 in 3 seconds.
VERBOSE: Error while making REST request to Azure API.
VERBOSE: Retrying 2/5 in 3 seconds.
VERBOSE: Error while making REST request to Azure API.
VERBOSE: Retrying 3/5 in 3 seconds.
VERBOSE: Error while making REST request to Azure API.
VERBOSE: Retrying 4/5 in 3 seconds.
VERBOSE: Error while making REST request to Azure API.
VERBOSE: Retrying 5/5 in 3 seconds.
Invoke-ZaAzureMonitorApiQuery: /usr/lib/zabbix/externalscripts/helpers/Get-ZaAzureMonitorMetricValue.ps1:76
Line |
76 | … $response = Invoke-ZaAzureMonitorApiQuery -authHeader $authHeader -qu …
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
| Error while making REST request to Azure API. 5 retries were made.
Reply | Reply with quote | Quote
Super User
0 # Fixed?Super User 2020-07-02 10:07
Hi!

Take a look at that:
github.com/vicioussn/zabbix-azure/commit/92c41f55b1e1506d97746d0316ed81fe735f72e8#diff-915335a6fa377f86a14a6a6d62bfc3a8

With this you will get the detailed error output coming from Azure API.
Reply | Reply with quote | Quote
JoseM
0 # RE: Fixed?JoseM 2020-07-02 17:03
Quoting Super User:
Hi!

Take a look at that:
github.com/vicioussn/zabbix-azure/commit/92c41f55b1e1506d97746d0316ed81fe735f72e8#diff-915335a6fa377f86a14a6a6d62bfc3a8

With this you will get the detailed error output coming from Azure API.


This is the error:
{"code":"BadRequest","message":"End time: 7/2/2020 2:55:03 PM must be at least 1 minute later than start time: 7/2/2020
| 7:42:00 PM, traceId: {4c279006-2129-4293-b5c9-128090f12e9a}"}

i don't understand what's the problem. can you help me?
Reply | Reply with quote | Quote
Super User
0 # RE: Fixed?Super User 2020-07-03 17:09
Quoting JoseM:

This is the error:
{"code":"BadRequest","message":"End time: 7/2/2020 2:55:03 PM must be at least 1 minute later than start time: 7/2/2020
| 7:42:00 PM, traceId: {4c279006-2129-4293-b5c9-128090f12e9a}"}

i don't understand what's the problem. can you help me?


That's very strange ... Drop here please URL it's trying to reach for metrics (the line after the "VERBOSE: Building URI to pull metrics from Azure Monitor.")
Reply | Reply with quote | Quote
JoseM
0 # RE: Fixed?JoseM 2020-07-03 21:27
Quoting Super User:

That's very strange ... Drop here please URL it's trying to reach for metrics (the line after the "VERBOSE: Building URI to pull metrics from Azure Monitor.")


Here's the output log:

VERBOSE: Item 45/84
VERBOSE: Parsing item key 'azure.resource[LINUX-TEST,virtualMachines,Data Disk Queue Depth,PT1M,Average]' and getting variables to make REST request.
VERBOSE: Getting time span for item 'Data Disk Queue Depth (Preview) - LINUX-TEST' (id=86687) to determine period to pull metrics from Azure.
VERBOSE: Getting Zabbix history for item '86687'.
VERBOSE: Successfully fetched Zabbix history for item '86687'.
VERBOSE: Timespan = '2020-07-02T19:42:00Z - 2020-07-02T15:13:25Z'.
VERBOSE: Logging to Azure.
VERBOSE: Azure Monitor API header built.
VERBOSE: Getting metric values from Azure Monitor with parameters:
VERBOSE: - resourceName = 'LINUX-TEST'
VERBOSE: - resourceType = 'virtualMachines'
VERBOSE: - subscriptionId = 'ece9a1a6-d2d7-4284-b2fd-865d967c7024'
VERBOSE: - resourceGroupName = 'FISA-TEST';
VERBOSE: - timeSpan = '2020-07-02T19:42:00Z - 2020-07-02T15:13:25Z'
VERBOSE: - timeGrain = 'PT1M'
VERBOSE: - metricName = 'Data Disk Queue Depth'
VERBOSE: Building URI to pull metrics from Azure Monitor.
VERBOSE: URI: management.azure.com/subscriptions/ece9a1a6-d2d7-4284-b2fd-865d967c7024/resourceGroups/FISA-TEST/providers/Microsoft.Compute/virtualMachines/LINUX-TEST/providers/microsoft.insights/metrics?timespan=2020-07-02T19:42:00Z/2020-07-02T15:13:25Z&interval=PT1M&api-version=2018-01-01&metricnames=Data Disk Queue Depth&aggregation=Average
**********************
Command start time: 20200702101626
**********************
PS>TerminatingError(Invoke-RestMethod): "{"code":"BadRequest","message":"End time: 7/2/2020 3:13:25 PM must be at least 1 minute later than start time: 7/2/2020 7:42:00 PM, traceId: {3e799c75-afb7-4596-b85a-48967dd6d293}"}"
VERBOSE: Error while making REST request to Azure API.
VERBOSE: Retrying 1/5 in 3 seconds.
**********************
Command start time: 20200702101630
**********************
PS>TerminatingError(Invoke-RestMethod): "{"code":"BadRequest","message":"End time: 7/2/2020 3:13:25 PM must be at least 1 minute later than start time: 7/2/2020 7:42:00 PM, traceId: {b0d8ba88-c5f7-4f34-b40e-3452959e6fa6}"}"
VERBOSE: Error while making REST request to Azure API.
VERBOSE: Retrying 2/5 in 3 seconds.
**********************
Command start time: 20200702101634
**********************
PS>TerminatingError(Invoke-RestMethod): "{"code":"BadRequest","message":"End time: 7/2/2020 3:13:25 PM must be at least 1 minute later than start time: 7/2/2020 7:42:00 PM, traceId: {b71e949a-b0e1-48d6-aa59-89fd3fb47ce6}"}"
VERBOSE: Error while making REST request to Azure API.
VERBOSE: Retrying 3/5 in 3 seconds.
**********************
Command start time: 20200702101638
**********************
PS>TerminatingError(Invoke-RestMethod): "{"code":"BadRequest","message":"End time: 7/2/2020 3:13:25 PM must be at least 1 minute later than start time: 7/2/2020 7:42:00 PM, traceId: {169e0ec6-776f-428c-8252-831a7d7f4923}"}"
VERBOSE: Error while making REST request to Azure API.
VERBOSE: Retrying 4/5 in 3 seconds.
**********************
Command start time: 20200702101641
**********************
PS>TerminatingError(Invoke-RestMethod): "{"code":"BadRequest","message":"End time: 7/2/2020 3:13:25 PM must be at least 1 minute later than start time: 7/2/2020 7:42:00 PM, traceId: {351019bf-60e5-4838-9935-c071d266f223}"}"
VERBOSE: Error while making REST request to Azure API.
VERBOSE: Retrying 5/5 in 3 seconds.
**********************
Command start time: 20200702101645
**********************
PS>TerminatingError(Invoke-RestMethod): "{"code":"BadRequest","message":"End time: 7/2/2020 3:13:25 PM must be at least 1 minute later than start time: 7/2/2020 7:42:00 PM, traceId: {6964dfdc-9d84-4aad-a184-5a8a95e03271}"}"
VERBOSE: Error while making REST request to Azure API. 5 retries were made.
Removing lock file 'get-azure-metrics-values_Azure.lck'.
**********************
Command start time: 20200702101645
**********************
PS>TerminatingError(Invoke-RestMethod): "{"code":"BadRequest","message":"End time: 7/2/2020 3:13:25 PM must be at least 1 minute later than start time: 7/2/2020 7:42:00 PM, traceId: {6964dfdc-9d84-4aad-a184-5a8a95e03271}"}"
>> TerminatingError(Invoke-RestMethod): "{"code":"BadRequest","message":"End time: 7/2/2020 3:13:25 PM must be at least 1 minute later than start time: 7/2/2020 7:42:00 PM, traceId: {6964dfdc-9d84-4aad-a184-5a8a95e03271}"}"
>> TerminatingError(Invoke-RestMethod): "{"code":"BadRequest","message":"End time: 7/2/2020 3:13:25 PM must be at least 1 minute later than start time: 7/2/2020 7:42:00 PM, traceId: {6964dfdc-9d84-4aad-a184-5a8a95e03271}"}"
>> TerminatingError(Invoke-RestMethod): "{"code":"BadRequest","message":"End time: 7/2/2020 3:13:25 PM must be at least 1 minute later than start time: 7/2/2020 7:42:00 PM, traceId: {6964dfdc-9d84-4aad-a184-5a8a95e03271}"}"

Invoke-RestMethod: /usr/lib/zabbix/externalscripts/helpers/Invoke-ZaAzureMonitorApiQuery.ps1:40
Line |
40 | … $response = Invoke-RestMethod @params -Verbose:$false -ErrorAction St …
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
| {"code":"BadRequest","message":"End time: 7/2/2020 3:13:25 PM
| must be at least 1 minute later than start time: 7/2/2020
| 7:42:00 PM, traceId: {6964dfdc-9d84-4aad-a184-5a8a95e03271}"}

**********************
PowerShell transcript end
End time: 20200702101645
**********************
Reply | Reply with quote | Quote
Super User
0 # RE: Fixed?Super User 2020-07-06 12:21
Hi!

Here's your problem:
VERBOSE: Timespan = '2020-07-02T19:42:00Z - 2020-07-02T15:13:25Z'.
As you can see, the first time is later than the last block. There's some problem with time conversion.

I added more logging:
github.com/vicioussn/zabbix-azure/commit/00ea9e387ff20917da18dfd3724b254424705bcc

Please put here same logs after applying new code.
Btw, what's the time zone of your Zabbix host?
Reply | Reply with quote | Quote
JoseM
0 # RE: Fixed?JoseM 2020-07-06 16:43
Quoting Super User:
Hi!

Here's your problem:
VERBOSE: Timespan = '2020-07-02T19:42:00Z - 2020-07-02T15:13:25Z'.
As you can see, the first time is later than the last block. There's some problem with time conversion.

I added more logging:
github.com/vicioussn/zabbix-azure/commit/00ea9e387ff20917da18dfd3724b254424705bcc

Please put here same logs after applying new code.
Btw, what's the time zone of your Zabbix host?


Here's the output after add the lines:
VERBOSE: Item 24/147
VERBOSE: Parsing item key 'azure.resource[LINUX-TEST,virtualMachines,Data Disk Queue Depth,PT1M,Average]' and getting variables to make REST request.
VERBOSE: Getting time span for item 'Data Disk Queue Depth (Preview) - LINUX-TEST' (id=86687) to determine period to pull metrics from Azure.
VERBOSE: Getting Zabbix history for item '86687'.
VERBOSE: Successfully fetched Zabbix history for item '86687'.
VERBOSE: Latest timestamp for the item: 1594044780.
VERBOSE: Current Epoch time (-3 minutes): 1594046154.
VERBOSE: Timespan = '2020-07-06T19:13:00Z - 2020-07-06T14:35:54Z'.
VERBOSE: Logging to Azure.
VERBOSE: Azure Monitor API header built.
VERBOSE: Getting metric values from Azure Monitor with parameters:
VERBOSE: - resourceName = 'LINUX-TEST'
VERBOSE: - resourceType = 'virtualMachines'
VERBOSE: - subscriptionId = 'ece9a1a6-d2d7-4284-b2fd-865d967c7024'
VERBOSE: - resourceGroupName = 'FISA-TEST';
VERBOSE: - timeSpan = '2020-07-06T19:13:00Z - 2020-07-06T14:35:54Z'
VERBOSE: - timeGrain = 'PT1M'
VERBOSE: - metricName = 'Data Disk Queue Depth'
VERBOSE: Building URI to pull metrics from Azure Monitor.
VERBOSE: URI: management.azure.com/subscriptions/ece9a1a6-d2d7-4284-b2fd-865d967c7024/resourceGroups/FISA-TEST/providers/Microsoft.Compute/virtualMachines/LINUX-TEST/providers/microsoft.insights/metrics?timespan=2020-07-06T19:13:00Z/2020-07-06T14:35:54Z&interval=PT1M&api-version=2018-01-01&metricnames=Data Disk Queue Depth&aggregation=Average
**********************
Command start time: 20200706093855
**********************
PS>TerminatingError(Invoke-RestMethod): "{"code":"BadRequest","message":"End time: 7/6/2020 2:35:54 PM must be at least 1 minute later than start time: 7/6/2020 7:13:00 PM, traceId: {da29900e-f912-4260-98cc-a85eb64f5436}"}"
VERBOSE: Error while making REST request to Azure API.
VERBOSE: Retrying 1/5 in 3 seconds.
**********************
Command start time: 20200706093859
**********************
PS>TerminatingError(Invoke-RestMethod): "{"code":"BadRequest","message":"End time: 7/6/2020 2:35:54 PM must be at least 1 minute later than start time: 7/6/2020 7:13:00 PM, traceId: {bf6ba87d-dba4-482d-84c1-a2372a2eb2d3}"}"
VERBOSE: Error while making REST request to Azure API.
VERBOSE: Retrying 2/5 in 3 seconds.
**********************
Command start time: 20200706093902
**********************
PS>TerminatingError(Invoke-RestMethod): "{"code":"BadRequest","message":"End time: 7/6/2020 2:35:54 PM must be at least 1 minute later than start time: 7/6/2020 7:13:00 PM, traceId: {87317371-e4a4-492e-a9dd-9916ff146668}"}"
VERBOSE: Error while making REST request to Azure API.
VERBOSE: Retrying 3/5 in 3 seconds.
**********************
Command start time: 20200706093906
**********************
PS>TerminatingError(Invoke-RestMethod): "{"code":"BadRequest","message":"End time: 7/6/2020 2:35:54 PM must be at least 1 minute later than start time: 7/6/2020 7:13:00 PM, traceId: {6ca49caa-ad9a-4aaf-8104-bba7688c4c31}"}"
VERBOSE: Error while making REST request to Azure API.
VERBOSE: Retrying 4/5 in 3 seconds.
**********************
Command start time: 20200706093910
**********************
PS>TerminatingError(Invoke-RestMethod): "{"code":"BadRequest","message":"End time: 7/6/2020 2:35:54 PM must be at least 1 minute later than start time: 7/6/2020 7:13:00 PM, traceId: {7318dcad-b943-42b7-a54a-f56c172411f5}"}"
VERBOSE: Error while making REST request to Azure API.
VERBOSE: Retrying 5/5 in 3 seconds.
**********************
Command start time: 20200706093914
**********************
PS>TerminatingError(Invoke-RestMethod): "{"code":"BadRequest","message":"End time: 7/6/2020 2:35:54 PM must be at least 1 minute later than start time: 7/6/2020 7:13:00 PM, traceId: {e7f2e4bd-ad25-404c-a7cc-29af5d2540cc}"}"
VERBOSE: Error while making REST request to Azure API. 5 retries were made.
Removing lock file 'get-azure-metrics-values_Azure.lck'.
**********************
Command start time: 20200706093914
**********************
PS>TerminatingError(Invoke-RestMethod): "{"code":"BadRequest","message":"End time: 7/6/2020 2:35:54 PM must be at least 1 minute later than start time: 7/6/2020 7:13:00 PM, traceId: {e7f2e4bd-ad25-404c-a7cc-29af5d2540cc}"}"
>> TerminatingError(Invoke-RestMethod): "{"code":"BadRequest","message":"End time: 7/6/2020 2:35:54 PM must be at least 1 minute later than start time: 7/6/2020 7:13:00 PM, traceId: {e7f2e4bd-ad25-404c-a7cc-29af5d2540cc}"}"
>> TerminatingError(Invoke-RestMethod): "{"code":"BadRequest","message":"End time: 7/6/2020 2:35:54 PM must be at least 1 minute later than start time: 7/6/2020 7:13:00 PM, traceId: {e7f2e4bd-ad25-404c-a7cc-29af5d2540cc}"}"
>> TerminatingError(Invoke-RestMethod): "{"code":"BadRequest","message":"End time: 7/6/2020 2:35:54 PM must be at least 1 minute later than start time: 7/6/2020 7:13:00 PM, traceId: {e7f2e4bd-ad25-404c-a7cc-29af5d2540cc}"}"
{"code":"BadRequest","message":"End time: 7/6/2020 2:35:54 PM must be at least 1 minute later than start time: 7/6/2020 7:13:00 PM, traceId: {e7f2e4bd-ad25-404c-a7cc-29af5d2540cc}"}

Invoke-RestMethod: /usr/lib/zabbix/externalscripts/helpers/Invoke-ZaAzureMonitorApiQuery.ps1:40
Line |
40 | … $response = Invoke-RestMethod @params -Verbose:$false -ErrorAction St …
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
| {"code":"BadRequest","message":"End time: 7/6/2020 2:35:54 PM must be at least 1 minute later than start time: 7/6/2020
| 7:13:00 PM, traceId: {e7f2e4bd-ad25-404c-a7cc-29af5d2540cc}"}

**********************
PowerShell transcript end
End time: 20200706093914
**********************

My time zone is gmt -5 bogota.
Reply | Reply with quote | Quote
Super User
0 # RE: Fixed?Super User 2020-07-06 20:28
Looks like some problem with time conversion Epoch -> Windows.

I'll take a look tomorrow.
Reply | Reply with quote | Quote
Super User
0 # RE: Fixed?Super User 2020-07-06 20:31
Based on this...

VERBOSE: Latest timestamp for the item: 1594044780.
VERBOSE: Current Epoch time (-3 minutes): 1594046154.
VERBOSE: Timespan = '2020-07-06T19:13:00Z - 2020-07-06T14:35:54Z'.

...first conversion is incorrect
Reply | Reply with quote | Quote
Super User
0 # RE: Fixed?Super User 2020-07-07 09:50 Reply | Reply with quote | Quote
JoseM
0 # RE: Fixed?JoseM 2020-07-07 20:58
Quoting Super User:


Thank you, it's working really good now. i will like to work with you in a couple of improvements if you're ok.

Right now when an item is deleted in azure causes the abnormal stop of get metrics script.

Second, do you think if there's a way to use macros so create a template with a discover host rule that discover items on azure and create the host with a new template linked. someting like vmware template?
Reply | Reply with quote | Quote
Super User
0 # RE: Fixed?Super User 2020-07-08 09:24
Glad it finally fixed =).

For the first one: yep, I was thinking to sort this problem out. Please create an issue on GitHub to track it. May require a few days - I'm out of the project which was using Zabbix, so now it's like a hobby.

For your second request. Unfortunately I've never been working with host discovery, so I dont really know how it works. Maybe if you describe a full process - I'll think about implementation. But currently not in plans.
Reply | Reply with quote | Quote
JoseM
0 # RE: Fixed?JoseM 2020-07-08 16:15
Quoting Super User:
Glad it finally fixed =).

For the first one: yep, I was thinking to sort this problem out. Please create an issue on GitHub to track it. May require a few days - I'm out of the project which was using Zabbix, so now it's like a hobby.

For your second request. Unfortunately I've never been working with host discovery, so I dont really know how it works. Maybe if you describe a full process - I'll think about implementation. But currently not in plans.


Ok i'll submit the issue.

I know or i have the idea about the host discovery configuration, i can help you with it.
Reply | Reply with quote | Quote
Tony M
0 # Does this get metrics from Virtual Network Gateways?Tony M 2020-07-01 21:25
Specifically, I am needing to monitor VPN connections in Azure. Will this pull full metrics from a Virtual Network Gateway?
Reply | Reply with quote | Quote
Tony M
0 # VirtualNetworkGatewayTony M 2020-07-01 23:07
Hi, just wanted to say I was able to add Microsoft.Network to get VNG metrics! Works great!
Reply | Reply with quote | Quote
Super User
0 # RE: VirtualNetworkGatewaySuper User 2020-07-02 09:27
Quoting Tony M:
Hi, just wanted to say I was able to add Microsoft.Network to get VNG metrics! Works great!


Happy to hear that! =)
Reply | Reply with quote | Quote
Dave C
0 # GeekDave C 2020-07-09 18:12
Great piece of work there. Many thanks for this.
I'm having an issue with using the "Test Item" when attempt to run the discovery script in Zabbix. From the command line running :
./get.azure.metrics.sh vm

works perfectly.

When I run within Zabbix using "Test" on the discovery rule (I'm Zabbix 5.0) I'm getting a timeout message.
A manual execution of the script takes around 2 seconds and I've set the timeout in zabbix_server.conf to 10 seconds.

Any advice on how I can diagnose please?

Thanks in advance,
Dave
Reply | Reply with quote | Quote
Super User
0 # RE: GeekSuper User 2020-07-10 09:01
Hi!

I would do the following:

1. Check the output of 'top' command to get CPU load during execution of LLD script from the Zabbix. What's going on there?
2. Verify that LLD script is not configured to run every 1m. Make it to run every 1h.

If that wont answer the question - then my next step will be - to enable Powershell transcript for LLD script - just like i did here: github.com/vicioussn/zabbix-azure/blob/master/development/get.azure.metrics.values.ps1#L6
Reply | Reply with quote | Quote
E Bossis
+1 # RE: GeekE Bossis 2020-07-23 07:45
Has the same issue. Increased to 20 seconds in zabbix_server.conf and it solved it
Reply | Reply with quote | Quote
Ellison
0 # Failed CoreCLREllison 2020-09-11 22:22
Hello!

Congratulations on the initiative, very nice structure.

When performing a test, the following error is returned:
Failed to create CoreCLR, HRESULT: 0x80004005

And when it runs by scheduling the discovery this:
Invalid discovery rule value: cannot parse as a valid JSON object: invalid object format, expected opening character '{' or '[' at: 'Failed to create CoreCLR, HRESULT: 0x80004005'

Can you help me?
Reply | Reply with quote | Quote
Super User
0 # RE: Failed CoreCLRSuper User 2020-09-16 13:04
Hi!

This must be isolated to your VM - never saw this kind of issues.

Take a look at github.com/PowerShell/PowerShell/issues/13166 - maybe it will help.
Reply | Reply with quote | Quote
Willard
0 # [Updated] Monitoring Azure resources with ZabbixWillard 2020-09-15 14:53
Thanks for finally writing about >[Updated] Monitoring Azure resources with Zabbix
Reply | Reply with quote | Quote
Add comment