No description
Find a file
Gergin Darakov b3bcee469c
add CI and build steps
The commit adds Github Actions and Dockerfile for building a multi arch Go image
2023-11-26 22:46:33 +02:00
.github add CI and build steps 2023-11-26 22:46:33 +02:00
internal/collector add CI and build steps 2023-11-26 22:46:33 +02:00
opnsense add CI and build steps 2023-11-26 22:46:33 +02:00
vendor Add initial project structure 2023-11-26 16:06:03 +02:00
.dockerignore Add initial project structure 2023-11-26 16:06:03 +02:00
.gitignore Add initial project structure 2023-11-26 16:06:03 +02:00
.golangci.yml add CI and build steps 2023-11-26 22:46:33 +02:00
Dockerfile add CI and build steps 2023-11-26 22:46:33 +02:00
go.mod Add initial project structure 2023-11-26 16:06:03 +02:00
go.sum Add initial project structure 2023-11-26 16:06:03 +02:00
LICENSE add CI and build steps 2023-11-26 22:46:33 +02:00
main.go add CI and build steps 2023-11-26 22:46:33 +02:00
Makefile Add initial project structure 2023-11-26 16:06:03 +02:00
README.md add CI and build steps 2023-11-26 22:46:33 +02:00
VERSION add CI and build steps 2023-11-26 22:46:33 +02:00

OPNsense Prometheus Exporter

The OPNsense exporter enables you to monitor your OPNsense firewall from the API.

Still under heavy development. The full metrics list is not yet implemented.

Table of Contents

About OPNsense User Permissions
Usage
Configuration
- SSL/TLS
Grafana Dashboard

About

This exporter delivers an extensive range of OPNsense-specific metrics, sourced directly from the OPNsense API. Focusing specifically on OPNsense, this exporter provides metrics about OPNsense, the plugin ecosystem and the services running on the firewall. However, it's recommended to use it with node_exporter. You can combine the metrics from both exporters in Grafana and in your Alert System to create a dashboard that displays the full picture of your system.

While the node_exporter must be installed on the firewall itself, this exporter can be installed on any machine that has network access to the OPNsense API.

OPNsense user permissions

TODO

Usage

TODO

Configuration

To configure where your OPNsense API is located, you can use the following flags:

  • --opnsense.protocol - The protocol to use to connect to the OPNsense API. Can be either http or https.
  • --opnsense.address - The hostname or IP address of the OPNsense API.
  • --opnsense.api-key - The API key to use to connect to the OPNsense API.
  • --opnsense.api-secret - The API secret to use to connect to the OPNsense API
  • --exporter.instance-label - Label to use to identify the instance in every metric. If you have multiple instances of the exporter, you can differentiate them by using different value in this flag, that represents the instance of the target OPNsense.

SSL/TLS

If you have your api served with self-signed certificates. You should add them to the system trust store.

If you want to disable TLS certificate verification, you can use the following flag:

  • --opnsense.insecure - Disable TLS certificate verification. Defaults to false.

You can disable parts of the exporter using the following flags:

  • --exporter.disable-arp-table - Disable the scraping of the ARP table. Defaults to false.
  • --exporter.disable-cron-table - Disable the scraping of the cron table. Defaults to false.

You can disable the exporter metrics using the following flag:

  • --web.disable-exporter-metrics - Exclude metrics about the exporter itself (promhttp_, process_, go_*). Defaults to false.

Full list

Flags:
  -h, --[no-]help                Show context-sensitive help (also try --help-long and --help-man).
      --log.level="info"         Log level. One of: [debug, info, warn, error]
      --log.format="logfmt"      Log format. One of: [logfmt, json]
      --web.telemetry-path="/metrics"  
                                 Path under which to expose metrics.
      --[no-]web.disable-exporter-metrics  
                                 Exclude metrics about the exporter itself (promhttp_*, process_*, go_*). ($OPNSENSE_EXPORTER_DISABLE_EXPORTER_METRICS)
      --runtime.gomaxprocs=2     The target number of CPUs that the Go runtime will run on (GOMAXPROCS) ($GOMAXPROCS)
      --exporter.instance-label=EXPORTER.INSTANCE-LABEL  
                                 Label to use to identify the instance in every metric. If you have multiple instances of the exporter, you can differentiate them by using different value in this flag, that represents the instance of the target OPNsense.
                                 ($OPNSENSE_EXPORTER_INSTANCE_LABEL)
      --[no-]exporter.disable-arp-table  
                                 Disable the scraping of the ARP table ($OPNSENSE_EXPORTER_DISABLE_ARP_TABLE)
      --[no-]exporter.disable-cron-table  
                                 Disable the scraping of the cron table ($OPNSENSE_EXPORTER_DISABLE_CRON_TABLE)
      --opnsense.protocol=OPNSENSE.PROTOCOL  
                                 Protocol to use to connect to OPNsense API. One of: [http, https] ($OPNSENSE_EXPORTER_OPS_PROTOCOL)
      --opnsense.address=OPNSENSE.ADDRESS  
                                 Hostname or IP address of OPNsense API ($OPNSENSE_EXPORTER_OPS_API)
      --opnsense.api-key=OPNSENSE.API-KEY  
                                 API key to use to connect to OPNsense API ($OPNSENSE_EXPORTER_OPS_API_KEY)
      --opnsense.api-secret=OPNSENSE.API-SECRET  
                                 API secret to use to connect to OPNsense API ($OPNSENSE_EXPORTER_OPS_API_SECRET)
      --[no-]opnsense.insecure   Disable TLS certificate verification ($OPNSENSE_EXPORTER_OPS_INSECURE)
      --[no-]web.systemd-socket  Use systemd socket activation listeners instead of port listeners (Linux only).
      --web.listen-address=:8080 ...  
                                 Addresses on which to expose metrics and web interface. Repeatable for multiple addresses.
      --web.config.file=""       [EXPERIMENTAL] Path to configuration file that can enable TLS or authentication. See: https://github.com/prometheus/exporter-toolkit/blob/master/docs/web-configuration.md

Grafana Dashboard

TODO