ravualhemio / prometheus_aci_exporter Goto Github PK

View Code? Open in Web Editor NEW

16.0 5.0 14.0 89 KB

Cisco ACI exporter for Prometheus

License: Apache License 2.0

Python 98.70% Dockerfile 1.30%

cisco-aci prometheus-exporter

prometheus_aci_exporter's Introduction

Prometheus ACI Exporter

Cisco ACI exporter for Prometheus

Pulls information from an APIC using the REST API.

OpenMetrics support

Initial OpenMetrics support is available. OpenMetrics output is provided if the exporter has been started with the --web.openmetrics option and the client supplies an Accept: header including application/openmetrics-text. Otherwise, data is output in the Prometheus exposition format.

If OpenMetrics output is requested, the names of counter metrics are modified on-the-fly to match the new convention (the suffix _total is appended unless the metric name already ends with _total). It is strongly recommended to include the _total suffix in counter metric names in preparation for the eventual transition from the Prometheus exposition format to OpenMetrics.

Docker Image

https://hub.docker.com/r/ravualhemio/prometheus_aci_exporter

Running the Docker Image

...and mounting a custom aci.yml file.

docker run --rm -v ${PWD}/examples/aci.yml:/etc/prometheus_aci_exporter/aci.yml -p 9377:9377 -it ravualhemio/prometheus_aci_exporter

Building the Docker Image locally

docker build . -t ravualhemio/prometheus_aci_exporter

prometheus_aci_exporter's People

Contributors

Stargazers

Watchers

Forkers

yijxiang josdotso jqckb yuenkapo rtrentin73 chaoszhuo powpao hartman17 manofcolombia aaronnad micruzz82 ms500in insobi danfael

prometheus_aci_exporter's Issues

port descriptions added as labels

Feature request if it doesn't already exist.

Can the port descriptions be pulled and added to labels? I haven't been able to see this data in the current metric labels.

Change Request: Do not derive internal number types from config file number types.

Would it be agreeable/possible to derive the types from the APIC API itself?

see: google/jsonnet#683

I looked at this over in my fork: https://github.com/josdotso/prometheus_aci_exporter/pulls?q=is%3Apr+is%3Aclosed

Please let me know if I should PR my commits to your repo.

add metrics for smart licensing status

Internal business case at my employer: metrics for monitoring the Smart Licensing status of the fabric.

Feature Request: Adopt GitHub Releases pattern

Hello again. ref: #1

Would you be willing to tag Semantically-versioned GitHub Releases for this project in GitHub? If properly configured at DockerHub, this would allow version-pinned docker image tags to used by your users.

e.g. docker pull ravualhemio/prometheus_aci_exporter:0.1.0

Thanks,
Joshua

Bug : clashing series on aci_fan_xxx for APIC nodes

I discovered with Cortex (one of long-term storage of Prometheus) that this exporter is having a problem with aci_fan_rpm, specially with APIC nodes (node 1, 2 and 3 for me).

Here is an example of the /metrics :

aci_fan_rpm{className="eqptFanStats5min",fabric="fabric-dc1",node="1",pod="1",queryName="fan_rpm_stats",slot="4",slotType="ftslot"} 3100.0
aci_fan_rpm{className="eqptFanStats5min",fabric="fabric-dc1",node="1",pod="1",queryName="fan_rpm_stats",slot="4",slotType="ftslot"} 3700.0
aci_fan_rpm{className="eqptFanStats5min",fabric="fabric-dc1",node="1",pod="1",queryName="fan_rpm_stats",slot="4",slotType="ftslot"} 3100.0
aci_fan_rpm{className="eqptFanStats5min",fabric="fabric-dc1",node="1",pod="1",queryName="fan_rpm_stats",slot="4",slotType="ftslot"} 3600.0
aci_fan_rpm{className="eqptFanStats5min",fabric="fabric-dc1",node="1",pod="1",queryName="fan_rpm_stats",slot="4",slotType="ftslot"} 3100.0
aci_fan_rpm{className="eqptFanStats5min",fabric="fabric-dc1",node="1",pod="1",queryName="fan_rpm_stats",slot="4",slotType="ftslot"} 3600.0
aci_fan_rpm{className="eqptFanStats5min",fabric="fabric-dc1",node="1",pod="1",queryName="fan_rpm_stats",slot="4",slotType="ftslot"} 3100.0
aci_fan_rpm{className="eqptFanStats5min",fabric="fabric-dc1",node="1",pod="1",queryName="fan_rpm_stats",slot="4",slotType="ftslot"} 3600.0
aci_fan_rpm{className="eqptFanStats5min",fabric="fabric-dc1",node="1",pod="1",queryName="fan_rpm_stats",slot="4",slotType="ftslot"} 3100.0
aci_fan_rpm{className="eqptFanStats5min",fabric="fabric-dc1",node="1",pod="1",queryName="fan_rpm_stats",slot="4",slotType="ftslot"} 3600.0
aci_fan_rpm{className="eqptFanStats5min",fabric="fabric-dc1",node="1",pod="1",queryName="fan_rpm_stats",slot="4",slotType="ftslot"} 3100.0
aci_fan_rpm{className="eqptFanStats5min",fabric="fabric-dc1",node="1",pod="1",queryName="fan_rpm_stats",slot="4",slotType="ftslot"} 3600.0

Do you have an idea where it could come ?

ValueError: dictionary update sequence element #0 has length 1; 2 is required

$ docker run --rm -v /Users/test/git/prometheus_aci_exporter/examples/aci.yml:/etc/prometheus_aci_exporter/aci.yml -p 9377:9377 -it ravualhemio/prometheus_aci_exporter

Exception happened during processing of request from ('172.17.0.1', 57602)
Traceback (most recent call last):
File "/usr/local/lib/python3.8/socketserver.py", line 650, in process_request_thread
self.finish_request(request, client_address)
File "/usr/local/lib/python3.8/socketserver.py", line 360, in finish_request
self.RequestHandlerClass(request, client_address, self)
File "/usr/local/lib/python3.8/socketserver.py", line 720, in init
self.handle()
File "/usr/local/lib/python3.8/http/server.py", line 427, in handle
self.handle_one_request()
File "/usr/local/lib/python3.8/http/server.py", line 415, in handle_one_request
method()
File "./prometheus_aci_exporter.py", line 513, in do_GET
generated_lines = [
File "./prometheus_aci_exporter.py", line 513, in
generated_lines = [
File "./prometheus_aci_exporter.py", line 246, in collect
yield from self.collect_fabric(fabric_name, fabric, controller, common_queries)
File "./prometheus_aci_exporter.py", line 334, in collect_fabric
labels.update(updated_labels)
ValueError: dictionary update sequence element #0 has length 1; 2 is required