infoblox-exporter


Nameinfoblox-exporter JSON
Version 0.1.4 PyPI version JSON
download
home_pagehttps://github.com/thenodon/infoblox-exporter
SummaryA Prometheus exporter for Infoblox
upload_time2023-07-19 08:46:36
maintainer
docs_urlNone
authorthenodon
requires_python>=3.8
licenseGPLv3
keywords
VCS
bugtrack_url
requirements No requirements were recorded.
Travis-CI No Travis.
coveralls test coverage No coveralls.
            infoblox-exporter
----------------------
# Overview
The infoblox-exporter collect metrics from an infoblox master.
Currently, two types of metrics is supported:
- Member service and member node service managed by the master.
- DHCP utilization based on networks

# Metrics
## Members 
Service, member or nodes, are reported as a gauge state 1=WORKING, 0=FAILED, 2=UNKNOWN. 
Any services in the INACTIVE state are not included. 
For node services the label `node_ip` is added. If the node is part of a HA setup the value is an
ip address, if not the value is `NO_HA_IP`.

Example output for a member that have HA setup:
```commandline
# HELP infoblox_node_service_status_node_status Node service node_status 1=WORKING, 0=FAILED, 2=UNKNOWN
# TYPE infoblox_node_service_status_node_status gauge
infoblox_node_service_status_node_status{node_ip="10.99.0.141"} 1.0
infoblox_node_service_status_node_status{node_ip="10.99.0.142"} 1.0
# HELP infoblox_node_service_status_disk_usage Node service disk_usage 1=WORKING, 0=FAILED, 2=UNKNOWN
# TYPE infoblox_node_service_status_disk_usage gauge
infoblox_node_service_status_disk_usage{node_ip="10.99.0.141"} 1.0
infoblox_node_service_status_disk_usage{node_ip="10.99.0.142"} 1.0
# HELP infoblox_node_service_status_enet_lan Node service enet_lan 1=WORKING, 0=FAILED, 2=UNKNOWN
# TYPE infoblox_node_service_status_enet_lan gauge
infoblox_node_service_status_enet_lan{node_ip="10.99.0.141"} 1.0
infoblox_node_service_status_enet_lan{node_ip="10.99.0.142"} 1.0
# HELP infoblox_node_service_status_enet_ha Node service enet_ha 1=WORKING, 0=FAILED, 2=UNKNOWN
# TYPE infoblox_node_service_status_enet_ha gauge
infoblox_node_service_status_enet_ha{node_ip="10.99.0.141"} 1.0
infoblox_node_service_status_enet_ha{node_ip="10.99.0.142"} 1.0
# HELP infoblox_node_service_status_enet_mgmt Node service enet_mgmt 1=WORKING, 0=FAILED, 2=UNKNOWN
# TYPE infoblox_node_service_status_enet_mgmt gauge
infoblox_node_service_status_enet_mgmt{node_ip="10.99.0.141"} 1.0
infoblox_node_service_status_enet_mgmt{node_ip="10.99.0.142"} 1.0
# HELP infoblox_node_service_status_replication Node service replication 1=WORKING, 0=FAILED, 2=UNKNOWN
# TYPE infoblox_node_service_status_replication gauge
infoblox_node_service_status_replication{node_ip="10.99.0.141"} 1.0
infoblox_node_service_status_replication{node_ip="10.99.0.142"} 1.0
# HELP infoblox_node_service_status_db_object Node service db_object 1=WORKING, 0=FAILED, 2=UNKNOWN
# TYPE infoblox_node_service_status_db_object gauge
infoblox_node_service_status_db_object{node_ip="10.99.0.141"} 1.0
infoblox_node_service_status_db_object{node_ip="10.99.0.142"} 1.0
# HELP infoblox_node_service_status_fan Node service fan 1=WORKING, 0=FAILED, 2=UNKNOWN
# TYPE infoblox_node_service_status_fan gauge
infoblox_node_service_status_fan{identity="1",node_ip="10.99.0.141"} 1.0
infoblox_node_service_status_fan{identity="10.99.0.141"} 1.0
infoblox_node_service_status_fan{identity="2",node_ip="10.99.0.141"} 1.0
infoblox_node_service_status_fan{identity="10.99.0.141"} 1.0
infoblox_node_service_status_fan{identity="3",node_ip="10.99.0.141"} 1.0
infoblox_node_service_status_fan{identity="10.99.0.141"} 1.0
infoblox_node_service_status_fan{identity="1",node_ip="10.99.0.142"} 1.0
infoblox_node_service_status_fan{identity="10.99.0.142"} 1.0
infoblox_node_service_status_fan{identity="2",node_ip="10.99.0.142"} 1.0
infoblox_node_service_status_fan{identity="10.99.0.142"} 1.0
infoblox_node_service_status_fan{identity="3",node_ip="10.99.0.142"} 1.0
infoblox_node_service_status_fan{identity="10.99.0.142"} 1.0
# HELP infoblox_node_service_status_power_supply Node service power_supply 1=WORKING, 0=FAILED, 2=UNKNOWN
# TYPE infoblox_node_service_status_power_supply gauge
infoblox_node_service_status_power_supply{node_ip="10.99.0.141"} 1.0
infoblox_node_service_status_power_supply{node_ip="10.99.0.142"} 1.0
# HELP infoblox_node_service_status_ntp_sync Node service ntp_sync 1=WORKING, 0=FAILED, 2=UNKNOWN
# TYPE infoblox_node_service_status_ntp_sync gauge
infoblox_node_service_status_ntp_sync{node_ip="10.99.0.141"} 1.0
infoblox_node_service_status_ntp_sync{node_ip="10.99.0.142"} 1.0
# HELP infoblox_node_service_status_cpu_temp Node service cpu_temp 1=WORKING, 0=FAILED, 2=UNKNOWN
# TYPE infoblox_node_service_status_cpu_temp gauge
infoblox_node_service_status_cpu_temp{identity="1",node_ip="10.99.0.141"} 1.0
infoblox_node_service_status_cpu_temp{identity="10.99.0.141"} 1.0
infoblox_node_service_status_cpu_temp{identity="1",node_ip="10.99.0.142"} 1.0
infoblox_node_service_status_cpu_temp{identity="10.99.0.142"} 1.0
# HELP infoblox_node_service_status_sys_temp Node service sys_temp 1=WORKING, 0=FAILED, 2=UNKNOWN
# TYPE infoblox_node_service_status_sys_temp gauge
infoblox_node_service_status_sys_temp{node_ip="10.99.0.141"} 1.0
infoblox_node_service_status_sys_temp{node_ip="10.99.0.142"} 1.0
# HELP infoblox_node_service_status_cpu_usage Node service cpu_usage 1=WORKING, 0=FAILED, 2=UNKNOWN
# TYPE infoblox_node_service_status_cpu_usage gauge
infoblox_node_service_status_cpu_usage{node_ip="10.99.0.141"} 1.0
infoblox_node_service_status_cpu_usage{node_ip="10.99.0.141"} 1.0
infoblox_node_service_status_cpu_usage{node_ip="10.99.0.142"} 1.0
infoblox_node_service_status_cpu_usage{node_ip="10.99.0.142"} 1.0
# HELP infoblox_node_service_status_core_files Node service core_files 1=WORKING, 0=FAILED, 2=UNKNOWN
# TYPE infoblox_node_service_status_core_files gauge
infoblox_node_service_status_core_files{node_ip="10.99.0.141"} 1.0
infoblox_node_service_status_core_files{node_ip="10.99.0.142"} 1.0
# HELP infoblox_node_service_status_memory Node service memory 1=WORKING, 0=FAILED, 2=UNKNOWN
# TYPE infoblox_node_service_status_memory gauge
infoblox_node_service_status_memory{node_ip="10.99.0.141"} 1.0
infoblox_node_service_status_memory{node_ip="10.99.0.142"} 1.0
# HELP infoblox_node_service_status_swap_usage Node service swap_usage 1=WORKING, 0=FAILED, 2=UNKNOWN
# TYPE infoblox_node_service_status_swap_usage gauge
infoblox_node_service_status_swap_usage{node_ip="10.99.0.141"} 1.0
infoblox_node_service_status_swap_usage{node_ip="10.99.0.142"} 1.0
# HELP infoblox_node_service_status_discovery_capacity Node service discovery_capacity 1=WORKING, 0=FAILED, 2=UNKNOWN
# TYPE infoblox_node_service_status_discovery_capacity gauge
infoblox_node_service_status_discovery_capacity{node_ip="10.99.0.141"} 1.0
infoblox_node_service_status_discovery_capacity{node_ip="10.99.0.142"} 1.0
# HELP infoblox_node_service_status_vpn_cert Node service vpn_cert 1=WORKING, 0=FAILED, 2=UNKNOWN
# TYPE infoblox_node_service_status_vpn_cert gauge
infoblox_node_service_status_vpn_cert{node_ip="10.99.0.141"} 1.0
infoblox_node_service_status_vpn_cert{node_ip="10.99.0.142"} 1.0
# HELP infoblox_service_status_dhcp Service dhcp 1=WORKING, 0=FAILED, 2=UNKNOWN
# TYPE infoblox_service_status_dhcp gauge
infoblox_service_status_dhcp 1.0
# HELP infoblox_service_status_dns Service dns 1=WORKING, 0=FAILED, 2=UNKNOWN
# TYPE infoblox_service_status_dns gauge
infoblox_service_status_dns 1.0
# HELP infoblox_service_status_dot_doh Service dot_doh 1=WORKING, 0=FAILED, 2=UNKNOWN
# TYPE infoblox_service_status_dot_doh gauge
infoblox_service_status_dot_doh 2.0
# HELP infoblox_service_status_ntp Service ntp 1=WORKING, 0=FAILED, 2=UNKNOWN
# TYPE infoblox_service_status_ntp gauge
infoblox_service_status_ntp 1.0
# HELP infoblox_service_status_hsm Service hsm 1=WORKING, 0=FAILED, 2=UNKNOWN
# TYPE infoblox_service_status_hsm gauge
infoblox_service_status_hsm 2.0
# HELP infoblox_service_status_reporting Service reporting 1=WORKING, 0=FAILED, 2=UNKNOWN
# TYPE infoblox_service_status_reporting gauge
infoblox_service_status_reporting 1.0
# HELP infoblox_service_status_imc_dca_bwl Service imc_dca_bwl 1=WORKING, 0=FAILED, 2=UNKNOWN
# TYPE infoblox_service_status_imc_dca_bwl gauge
infoblox_service_status_imc_dca_bwl 2.0
# HELP infoblox_node_info Node info info
# TYPE infoblox_node_info gauge
infoblox_node_info{ha_status="PASSIVE",hwid="0805201903700276",hwtype="IB-815",node_ip="10.99.0.141",platform="PHYSICAL"} 1.0
infoblox_node_info{ha_status="ACTIVE",hwid="0805201903700277",hwtype="IB-815",node_ip="10.99.0.142",platform="PHYSICAL"} 1.0
# HELP infoblox_up Infoblox API up
# TYPE infoblox_up gauge
infoblox_up 1.0
# HELP infoblox_scrape_time_seconds Infoblox API scrape time
# TYPE infoblox_scrape_time_seconds gauge
infoblox_scrape_time_seconds 0.33961824301513843

```
In addition to all the service metrics there is also `infoblox_node_info` with additional metadata 
labels. Metrics value is always 1.0

The `infoblox_up` is set to 1.0 if the exporter could connect to the Infoblox master and that the 
member exists.

## DHCP utilization
For a specific network that the infoblox master manage the metrics show the utilization of DCHP 
addresses. This can be valuable to alert on if the metrics is close to 1.0, 100 % utilization  

```commandline
# HELP infoblox_dhcp_utilization_ratio DHCP utilization ratio
# TYPE infoblox_dhcp_utilization_ratio gauge
infoblox_dhcp_utilization_ratio{network="140.166.134.128/26"} 0.212
# HELP infoblox_up Infoblox API up
# TYPE infoblox_up gauge
infoblox_up 1.0
# HELP infoblox_scrape_time_seconds Infoblox API scrape time
# TYPE infoblox_scrape_time_seconds gauge
infoblox_scrape_time_seconds 0.28882534499280155

```
# Discovery 
Please see the [infoblox-discovery](https://github.com/thenodon/infoblox_discovery)
to get dynamic Prometheus discovery configuration for   

# Environment variables

The following variables ar mandatory to set.

- BASIC_AUTH_USERNAME - the basic auth username to the exporter
- BASIC_AUTH_PASSWORD - the basic auth password to the exporter 
- INFOBLOX_MASTER - the ip/fqdn to the infoblox server
- INFOBLOX_WAPI_VERSION - the Infoblox master api version
- INFOBLOX_USERNAME - the Infoblox master username
- INFOBLOX_PASSWORD  - the Infoblox master password

The following are optional
- EXPORTER_HOST - default to `0.0.0.0`
- EXPORTER_PORT - default to `9597`
- EXPORTER_LOG_LEVEL - default to `INFO`

# Test
```
curl -s 'localhost:9597/probe?target=host.foo.com&module=member_services' 
```

The `type` can have the following values:
- member_services - the target is infoblox member
- dhcp_utilization - the target has to be network like `10.121.151.128/26`

            

Raw data

            {
    "_id": null,
    "home_page": "https://github.com/thenodon/infoblox-exporter",
    "name": "infoblox-exporter",
    "maintainer": "",
    "docs_url": null,
    "requires_python": ">=3.8",
    "maintainer_email": "",
    "keywords": "",
    "author": "thenodon",
    "author_email": "aha@ingby.com",
    "download_url": "https://files.pythonhosted.org/packages/8c/06/c143cccd49be6b8d7a2f19e5671ae461f6a06e7ddca8534290c4b095a5c2/infoblox-exporter-0.1.4.tar.gz",
    "platform": null,
    "description": "infoblox-exporter\n----------------------\n# Overview\nThe infoblox-exporter collect metrics from an infoblox master.\nCurrently, two types of metrics is supported:\n- Member service and member node service managed by the master.\n- DHCP utilization based on networks\n\n# Metrics\n## Members \nService, member or nodes, are reported as a gauge state 1=WORKING, 0=FAILED, 2=UNKNOWN. \nAny services in the INACTIVE state are not included. \nFor node services the label `node_ip` is added. If the node is part of a HA setup the value is an\nip address, if not the value is `NO_HA_IP`.\n\nExample output for a member that have HA setup:\n```commandline\n# HELP infoblox_node_service_status_node_status Node service node_status 1=WORKING, 0=FAILED, 2=UNKNOWN\n# TYPE infoblox_node_service_status_node_status gauge\ninfoblox_node_service_status_node_status{node_ip=\"10.99.0.141\"} 1.0\ninfoblox_node_service_status_node_status{node_ip=\"10.99.0.142\"} 1.0\n# HELP infoblox_node_service_status_disk_usage Node service disk_usage 1=WORKING, 0=FAILED, 2=UNKNOWN\n# TYPE infoblox_node_service_status_disk_usage gauge\ninfoblox_node_service_status_disk_usage{node_ip=\"10.99.0.141\"} 1.0\ninfoblox_node_service_status_disk_usage{node_ip=\"10.99.0.142\"} 1.0\n# HELP infoblox_node_service_status_enet_lan Node service enet_lan 1=WORKING, 0=FAILED, 2=UNKNOWN\n# TYPE infoblox_node_service_status_enet_lan gauge\ninfoblox_node_service_status_enet_lan{node_ip=\"10.99.0.141\"} 1.0\ninfoblox_node_service_status_enet_lan{node_ip=\"10.99.0.142\"} 1.0\n# HELP infoblox_node_service_status_enet_ha Node service enet_ha 1=WORKING, 0=FAILED, 2=UNKNOWN\n# TYPE infoblox_node_service_status_enet_ha gauge\ninfoblox_node_service_status_enet_ha{node_ip=\"10.99.0.141\"} 1.0\ninfoblox_node_service_status_enet_ha{node_ip=\"10.99.0.142\"} 1.0\n# HELP infoblox_node_service_status_enet_mgmt Node service enet_mgmt 1=WORKING, 0=FAILED, 2=UNKNOWN\n# TYPE infoblox_node_service_status_enet_mgmt gauge\ninfoblox_node_service_status_enet_mgmt{node_ip=\"10.99.0.141\"} 1.0\ninfoblox_node_service_status_enet_mgmt{node_ip=\"10.99.0.142\"} 1.0\n# HELP infoblox_node_service_status_replication Node service replication 1=WORKING, 0=FAILED, 2=UNKNOWN\n# TYPE infoblox_node_service_status_replication gauge\ninfoblox_node_service_status_replication{node_ip=\"10.99.0.141\"} 1.0\ninfoblox_node_service_status_replication{node_ip=\"10.99.0.142\"} 1.0\n# HELP infoblox_node_service_status_db_object Node service db_object 1=WORKING, 0=FAILED, 2=UNKNOWN\n# TYPE infoblox_node_service_status_db_object gauge\ninfoblox_node_service_status_db_object{node_ip=\"10.99.0.141\"} 1.0\ninfoblox_node_service_status_db_object{node_ip=\"10.99.0.142\"} 1.0\n# HELP infoblox_node_service_status_fan Node service fan 1=WORKING, 0=FAILED, 2=UNKNOWN\n# TYPE infoblox_node_service_status_fan gauge\ninfoblox_node_service_status_fan{identity=\"1\",node_ip=\"10.99.0.141\"} 1.0\ninfoblox_node_service_status_fan{identity=\"10.99.0.141\"} 1.0\ninfoblox_node_service_status_fan{identity=\"2\",node_ip=\"10.99.0.141\"} 1.0\ninfoblox_node_service_status_fan{identity=\"10.99.0.141\"} 1.0\ninfoblox_node_service_status_fan{identity=\"3\",node_ip=\"10.99.0.141\"} 1.0\ninfoblox_node_service_status_fan{identity=\"10.99.0.141\"} 1.0\ninfoblox_node_service_status_fan{identity=\"1\",node_ip=\"10.99.0.142\"} 1.0\ninfoblox_node_service_status_fan{identity=\"10.99.0.142\"} 1.0\ninfoblox_node_service_status_fan{identity=\"2\",node_ip=\"10.99.0.142\"} 1.0\ninfoblox_node_service_status_fan{identity=\"10.99.0.142\"} 1.0\ninfoblox_node_service_status_fan{identity=\"3\",node_ip=\"10.99.0.142\"} 1.0\ninfoblox_node_service_status_fan{identity=\"10.99.0.142\"} 1.0\n# HELP infoblox_node_service_status_power_supply Node service power_supply 1=WORKING, 0=FAILED, 2=UNKNOWN\n# TYPE infoblox_node_service_status_power_supply gauge\ninfoblox_node_service_status_power_supply{node_ip=\"10.99.0.141\"} 1.0\ninfoblox_node_service_status_power_supply{node_ip=\"10.99.0.142\"} 1.0\n# HELP infoblox_node_service_status_ntp_sync Node service ntp_sync 1=WORKING, 0=FAILED, 2=UNKNOWN\n# TYPE infoblox_node_service_status_ntp_sync gauge\ninfoblox_node_service_status_ntp_sync{node_ip=\"10.99.0.141\"} 1.0\ninfoblox_node_service_status_ntp_sync{node_ip=\"10.99.0.142\"} 1.0\n# HELP infoblox_node_service_status_cpu_temp Node service cpu_temp 1=WORKING, 0=FAILED, 2=UNKNOWN\n# TYPE infoblox_node_service_status_cpu_temp gauge\ninfoblox_node_service_status_cpu_temp{identity=\"1\",node_ip=\"10.99.0.141\"} 1.0\ninfoblox_node_service_status_cpu_temp{identity=\"10.99.0.141\"} 1.0\ninfoblox_node_service_status_cpu_temp{identity=\"1\",node_ip=\"10.99.0.142\"} 1.0\ninfoblox_node_service_status_cpu_temp{identity=\"10.99.0.142\"} 1.0\n# HELP infoblox_node_service_status_sys_temp Node service sys_temp 1=WORKING, 0=FAILED, 2=UNKNOWN\n# TYPE infoblox_node_service_status_sys_temp gauge\ninfoblox_node_service_status_sys_temp{node_ip=\"10.99.0.141\"} 1.0\ninfoblox_node_service_status_sys_temp{node_ip=\"10.99.0.142\"} 1.0\n# HELP infoblox_node_service_status_cpu_usage Node service cpu_usage 1=WORKING, 0=FAILED, 2=UNKNOWN\n# TYPE infoblox_node_service_status_cpu_usage gauge\ninfoblox_node_service_status_cpu_usage{node_ip=\"10.99.0.141\"} 1.0\ninfoblox_node_service_status_cpu_usage{node_ip=\"10.99.0.141\"} 1.0\ninfoblox_node_service_status_cpu_usage{node_ip=\"10.99.0.142\"} 1.0\ninfoblox_node_service_status_cpu_usage{node_ip=\"10.99.0.142\"} 1.0\n# HELP infoblox_node_service_status_core_files Node service core_files 1=WORKING, 0=FAILED, 2=UNKNOWN\n# TYPE infoblox_node_service_status_core_files gauge\ninfoblox_node_service_status_core_files{node_ip=\"10.99.0.141\"} 1.0\ninfoblox_node_service_status_core_files{node_ip=\"10.99.0.142\"} 1.0\n# HELP infoblox_node_service_status_memory Node service memory 1=WORKING, 0=FAILED, 2=UNKNOWN\n# TYPE infoblox_node_service_status_memory gauge\ninfoblox_node_service_status_memory{node_ip=\"10.99.0.141\"} 1.0\ninfoblox_node_service_status_memory{node_ip=\"10.99.0.142\"} 1.0\n# HELP infoblox_node_service_status_swap_usage Node service swap_usage 1=WORKING, 0=FAILED, 2=UNKNOWN\n# TYPE infoblox_node_service_status_swap_usage gauge\ninfoblox_node_service_status_swap_usage{node_ip=\"10.99.0.141\"} 1.0\ninfoblox_node_service_status_swap_usage{node_ip=\"10.99.0.142\"} 1.0\n# HELP infoblox_node_service_status_discovery_capacity Node service discovery_capacity 1=WORKING, 0=FAILED, 2=UNKNOWN\n# TYPE infoblox_node_service_status_discovery_capacity gauge\ninfoblox_node_service_status_discovery_capacity{node_ip=\"10.99.0.141\"} 1.0\ninfoblox_node_service_status_discovery_capacity{node_ip=\"10.99.0.142\"} 1.0\n# HELP infoblox_node_service_status_vpn_cert Node service vpn_cert 1=WORKING, 0=FAILED, 2=UNKNOWN\n# TYPE infoblox_node_service_status_vpn_cert gauge\ninfoblox_node_service_status_vpn_cert{node_ip=\"10.99.0.141\"} 1.0\ninfoblox_node_service_status_vpn_cert{node_ip=\"10.99.0.142\"} 1.0\n# HELP infoblox_service_status_dhcp Service dhcp 1=WORKING, 0=FAILED, 2=UNKNOWN\n# TYPE infoblox_service_status_dhcp gauge\ninfoblox_service_status_dhcp 1.0\n# HELP infoblox_service_status_dns Service dns 1=WORKING, 0=FAILED, 2=UNKNOWN\n# TYPE infoblox_service_status_dns gauge\ninfoblox_service_status_dns 1.0\n# HELP infoblox_service_status_dot_doh Service dot_doh 1=WORKING, 0=FAILED, 2=UNKNOWN\n# TYPE infoblox_service_status_dot_doh gauge\ninfoblox_service_status_dot_doh 2.0\n# HELP infoblox_service_status_ntp Service ntp 1=WORKING, 0=FAILED, 2=UNKNOWN\n# TYPE infoblox_service_status_ntp gauge\ninfoblox_service_status_ntp 1.0\n# HELP infoblox_service_status_hsm Service hsm 1=WORKING, 0=FAILED, 2=UNKNOWN\n# TYPE infoblox_service_status_hsm gauge\ninfoblox_service_status_hsm 2.0\n# HELP infoblox_service_status_reporting Service reporting 1=WORKING, 0=FAILED, 2=UNKNOWN\n# TYPE infoblox_service_status_reporting gauge\ninfoblox_service_status_reporting 1.0\n# HELP infoblox_service_status_imc_dca_bwl Service imc_dca_bwl 1=WORKING, 0=FAILED, 2=UNKNOWN\n# TYPE infoblox_service_status_imc_dca_bwl gauge\ninfoblox_service_status_imc_dca_bwl 2.0\n# HELP infoblox_node_info Node info info\n# TYPE infoblox_node_info gauge\ninfoblox_node_info{ha_status=\"PASSIVE\",hwid=\"0805201903700276\",hwtype=\"IB-815\",node_ip=\"10.99.0.141\",platform=\"PHYSICAL\"} 1.0\ninfoblox_node_info{ha_status=\"ACTIVE\",hwid=\"0805201903700277\",hwtype=\"IB-815\",node_ip=\"10.99.0.142\",platform=\"PHYSICAL\"} 1.0\n# HELP infoblox_up Infoblox API up\n# TYPE infoblox_up gauge\ninfoblox_up 1.0\n# HELP infoblox_scrape_time_seconds Infoblox API scrape time\n# TYPE infoblox_scrape_time_seconds gauge\ninfoblox_scrape_time_seconds 0.33961824301513843\n\n```\nIn addition to all the service metrics there is also `infoblox_node_info` with additional metadata \nlabels. Metrics value is always 1.0\n\nThe `infoblox_up` is set to 1.0 if the exporter could connect to the Infoblox master and that the \nmember exists.\n\n## DHCP utilization\nFor a specific network that the infoblox master manage the metrics show the utilization of DCHP \naddresses. This can be valuable to alert on if the metrics is close to 1.0, 100 % utilization  \n\n```commandline\n# HELP infoblox_dhcp_utilization_ratio DHCP utilization ratio\n# TYPE infoblox_dhcp_utilization_ratio gauge\ninfoblox_dhcp_utilization_ratio{network=\"140.166.134.128/26\"} 0.212\n# HELP infoblox_up Infoblox API up\n# TYPE infoblox_up gauge\ninfoblox_up 1.0\n# HELP infoblox_scrape_time_seconds Infoblox API scrape time\n# TYPE infoblox_scrape_time_seconds gauge\ninfoblox_scrape_time_seconds 0.28882534499280155\n\n```\n# Discovery \nPlease see the [infoblox-discovery](https://github.com/thenodon/infoblox_discovery)\nto get dynamic Prometheus discovery configuration for   \n\n# Environment variables\n\nThe following variables ar mandatory to set.\n\n- BASIC_AUTH_USERNAME - the basic auth username to the exporter\n- BASIC_AUTH_PASSWORD - the basic auth password to the exporter \n- INFOBLOX_MASTER - the ip/fqdn to the infoblox server\n- INFOBLOX_WAPI_VERSION - the Infoblox master api version\n- INFOBLOX_USERNAME - the Infoblox master username\n- INFOBLOX_PASSWORD  - the Infoblox master password\n\nThe following are optional\n- EXPORTER_HOST - default to `0.0.0.0`\n- EXPORTER_PORT - default to `9597`\n- EXPORTER_LOG_LEVEL - default to `INFO`\n\n# Test\n```\ncurl -s 'localhost:9597/probe?target=host.foo.com&module=member_services' \n```\n\nThe `type` can have the following values:\n- member_services - the target is infoblox member\n- dhcp_utilization - the target has to be network like `10.121.151.128/26`\n",
    "bugtrack_url": null,
    "license": "GPLv3",
    "summary": "A Prometheus exporter for Infoblox",
    "version": "0.1.4",
    "project_urls": {
        "Homepage": "https://github.com/thenodon/infoblox-exporter"
    },
    "split_keywords": [],
    "urls": [
        {
            "comment_text": "",
            "digests": {
                "blake2b_256": "99c88da33fb72de563ea8ca0a72f7711b5a46ca6c7b88f6d95da080f679f5793",
                "md5": "eba62a8d73bab417ed58abf646a3332f",
                "sha256": "00c7332ab06c9ebf01123c1fa7e1079c2ed0aa37b58de8fc7c0d95faa81a8932"
            },
            "downloads": -1,
            "filename": "infoblox_exporter-0.1.4-py3-none-any.whl",
            "has_sig": false,
            "md5_digest": "eba62a8d73bab417ed58abf646a3332f",
            "packagetype": "bdist_wheel",
            "python_version": "py3",
            "requires_python": ">=3.8",
            "size": 29435,
            "upload_time": "2023-07-19T08:46:34",
            "upload_time_iso_8601": "2023-07-19T08:46:34.682474Z",
            "url": "https://files.pythonhosted.org/packages/99/c8/8da33fb72de563ea8ca0a72f7711b5a46ca6c7b88f6d95da080f679f5793/infoblox_exporter-0.1.4-py3-none-any.whl",
            "yanked": false,
            "yanked_reason": null
        },
        {
            "comment_text": "",
            "digests": {
                "blake2b_256": "8c06c143cccd49be6b8d7a2f19e5671ae461f6a06e7ddca8534290c4b095a5c2",
                "md5": "856bbf45a8f7c053e9a378c3c40b96a8",
                "sha256": "2951a0f521072983954cc70282c1faba2433cb6a8b9bf1494b005100ee45d26f"
            },
            "downloads": -1,
            "filename": "infoblox-exporter-0.1.4.tar.gz",
            "has_sig": false,
            "md5_digest": "856bbf45a8f7c053e9a378c3c40b96a8",
            "packagetype": "sdist",
            "python_version": "source",
            "requires_python": ">=3.8",
            "size": 24722,
            "upload_time": "2023-07-19T08:46:36",
            "upload_time_iso_8601": "2023-07-19T08:46:36.131323Z",
            "url": "https://files.pythonhosted.org/packages/8c/06/c143cccd49be6b8d7a2f19e5671ae461f6a06e7ddca8534290c4b095a5c2/infoblox-exporter-0.1.4.tar.gz",
            "yanked": false,
            "yanked_reason": null
        }
    ],
    "upload_time": "2023-07-19 08:46:36",
    "github": true,
    "gitlab": false,
    "bitbucket": false,
    "codeberg": false,
    "github_user": "thenodon",
    "github_project": "infoblox-exporter",
    "travis_ci": false,
    "coveralls": false,
    "github_actions": true,
    "requirements": [],
    "lcname": "infoblox-exporter"
}
        
Elapsed time: 0.17707s