NETWAYS / NETWAYS/check_akcp_sensorprobeXplus
Filter for sensor specifically remotes thresholds
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
If you are using the plugin to collect all sensor data, you receive performance metrics for the sensors:
./check_akcp_sensorprobeXplus -h xx.xxx.xxx.xx -c community
[CRITICAL] - Device SPX+ Demo at location Hole (SPX+ F7 1.0.5233 May 12 2020 09:41:)
\_ [OK] Dual Humidity Port 1: 56.0%
\_ [OK] Dual Temperature Port 1: 23.5℃
\_ [OK] Temp Sensor Test: 23.7℃
\_ [CRITICAL] Motion Detector Port 4: Motion
\_ [OK] Icinga Demo: 0.0
|'Dual Humidity Port 1'=56%;32:66;23:69 'Dual Temperature Port 1'=23.5C;20.7:30;10.6:40 'Temp Sensor Test'=23.7C;20:30;10.5:40 'Motion Detector Port 4'=1 'Icinga Demo'=0
If you are filtering for specific sensors and ports, the thresholds are not added to the output:
./check_akcp_sensorprobeXplus -h xx.xxx.xxx.xx -c community --sensorPort 1 -m temperature
[OK] - Device SPX+ Demo at location Hole (SPX+ F7 1.0.5233 May 12 2020 09:41:)
\_ [OK] Temp Sensor Test: 23.7℃
|'Temp Sensor Test'=23.7C
While the plugin output is correct in case it is critical, the performance data thresholds are just missing.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start from the check_akcp_sensorprobeXplus command and compare performance-data generation for the unfiltered invocation with the --sensorPort 1 --sensorPort 1 -m temperature case shown in the report. Reproduce the missing thresholds using the example commands, then verify that filtered sensor output includes the same threshold values as the corresponding unfiltered output.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli, observability
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100