Skip to content

DIY Prometheus Exporter for PurpleAir API for ones home Grafana setup

License

Notifications You must be signed in to change notification settings

ViridianForge/purple_exporter

Repository files navigation

purple_exporter

MIT Licensed GitHub Super-Linter

Exporting metrics from the PurpleAir API for your PurpleAir Sensor.

This is where a link to the latest relase will go.

Table of Contents

  1. Description
  2. Technical Details
    1. Exposed Metrics
      1. Environmental Data
      2. Estimated Mass Concentrations
      3. Particle Concentrations
  3. Building Purple Exporter
    1. Getting an API Key
    2. Building from Source
    3. Building Docker Image
  4. Required Configuration
    1. Sensor Index
    2. API Read Key
    3. Request Rate
    4. Network Port
    5. Environmental Adjustment
    6. Log Level
  5. Running Purple Exporter
    1. Running from Source
    2. Running from Executable
    3. Running from Docker
  6. Grafana
  7. Testing
  8. License
  9. References

Description

purple_exporter is a Prometheus exporter that exports a subset of available information from a single PAII Purple Air Sensor.

This project was developed so I could pipe the information from my own PAII sensor to a grafana chart I run in my house. In the future, I may expand the usability of this exporter to other PA sensors, or ranges of sensors.

Technical Details

Exposed Metrics

Metrics are collected from all sensors for which they are available.

Environmental Data

  • Humidity: Relative humidity in the sensor chamber, on average, 4% lower than ambient humidity
  • Temperature: Temperature in the sensor chamber in Farenheit, on average 8F higher than ambient temperature
  • Air Pressure: Current pressure in millibars

Estimated Mass Concentrations

  • pm1.0: Estimated mass concentration of particles less than 1 uM in diameter. (ug/m^3)
  • pm2.5: Estimated mass concentration of particles less than 2.5 uM in diameter. (ug/m^3)
  • pm10.0: Estimated mass concentration of particles less than 10.0 uM in diameter. (ug/m^3)

Partical Concentrations

  • 0.3um: Count of particles greater than 0.3 uM in diameter. (particles/100mL)
  • 0.5um: Count of particles greater than 0.5 uM in diameter. (particles/100mL)
  • 1.0um: Count of particles greater than 1.0 uM in diameter. (particles/100mL)
  • 2.5um: Count of particles greater than 2.5 uM in diameter. (particles/100mL)
  • 5.0um: Count of particles greater than 5.0 uM in diameter. (particles/100mL)
  • 10.0um: Count of particles greater than 10.0 uM in diameter. (particles/100mL)

Building Purple Exporter

Getting an API Key

In order to use the exporter, one will need a PurpleAir API key. This can be obtained by e-mailing contact@purpleair.com. Approved applications will receive a read key, and a write key. This exporter only makes use of the read key to retrieve information from the specified sensor.

Building From Source

cargo build --release

The resulting executable will be placed in <path_to_repo>/target/release/.

Building Docker Image

If running from the repository root: docker build -t <tag> .

This will result in a trimmed down alpine linux image with a statically compiled executable.

Required Configuration

The exporter is configurable using the values below, specified via environmental variable, or command line argument.

Sensor Index

Set with the SENSOR_ID environment variable, or the -s flag. This value is the unique index assigned by PurpleAir to the sensor that readings will be drawn from.

API Read Key

Set with the READ_KEY environment variable, or the -x flag. This is one of the two API keys PurpleAir will furnish when following the above directions.

Request Rate

Set with the REQUEST_RATE environment variable, or the -r flag. This is how often to query the purple air API, in seconds. This will default to a minimum of once every 300 seconds (5 minutes).

Network Port

Set with the PORT environment variable, or the -p flag. This is the network port the exporter will serve its data from.

Environmental Adjustment

Set with the ADJUST environment variable, or the -a flag. This flag is used to indicate whether humidity and temperature readings should be adjusted to reflect likely ambient readings rather than readings in the sensor housing. Sensor readings are, on average, 8F hotter and 4% drier. Valid values are true or false, and will default to false.

Log Level

Set with RUST_LOG to indicate which level of messages to log when running purple_exporter. Options include: info or trace.

Running the Exporter

Running from Source

cargo run -- -r rate -s sensor_index -x API_read_key -p port -a adjust

Running from Executable

./purple_exporter -r rate -s sensor_index -x API_read_key -p port -a adjust

or by setting environment variables.

Running from Docker

docker run --env-file .env <image>

An example environment variable file is provided in .env.example.

Grafana

A Grafana dashboard for use with this exporter is available from the Grafana community library.

For direct importing into a Grafana instance, please use the packaged dashboard.json.

Testing

Work in Progress

License

LICENSE

References

About

DIY Prometheus Exporter for PurpleAir API for ones home Grafana setup

Resources

License

Stars

Watchers

Forks

Packages

No packages published