Title1
Checks historian tags and samples.
Install
Linux:
sudo pip3 install nagios_historian --upgrade
Also is possible to use:
sudo python3 -m pip install nagios_historian --upgrade
On windows with python3.5:
pip install nagios_historian --upgrade
For proxies add:
--proxy='http://user:passw@server:port'
Usage
Use the command line:
> nagios_historian --help
usage: nagios_historian [-h] [-u [URL]] [-e [EXTRA_ARGS]]
optional arguments:
-h, --help show this help message and exit
-u [URL], --url [URL]
url to check
--client_id
oauth2 client_id example client id: user01
--client_secret
oauth2 client_secret client password
--auth_url
oauth2 auth_url example: https://login.microsoftonline.com/company.onmicrosoft.com/oauth2/v2.0/token
--tags
tags names of historian
--instance
instance name of historian
--oauth2
Flag to use or not token for oauth2 before creating the request, used to check published services that uses azure oauth2
-e [EXTRA_ARGS], --extra_args [EXTRA_ARGS]
extra args
Example usage
Example use:
> nagios_historian -u “https://xxx/yyy/currentvalue?tagNames=” –client_id “admin1234” –client_secret “pass1234” –auth_url “https://xxxx/oauth/token” –oauth2 –tags “TAG1;TAG2;TAG3” –instance “INSTANCE”
Nagios config
Example command:
define command{
command_name check_nagios_historian
command_line /usr/local/bin/nagios_historian -u "$ARG1$" --client_id "$ARG2$" --client_secret "$ARG3$" --auth_url "$ARG4$" --oauth2 --tags "$ARG5$" --instance "$ARG6$" --extra_args='$ARG6$'
}
Example service:
define service {
host_name SERVERX
service_description service_name
check_command check_nagios_historian!http://url/path!admin123!pass1234!http://authurl/oauth2!Tags!Instance
use generic-service
notes some useful notes
}
You can use ansible role that already has the installation and command: https://github.com/CoffeeITWorks/ansible_nagios4_server_plugins
TODO
Use hash passwords
Add Unit tests?
Metadata
Release files for nagios-historian 0.7.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| nagios_historian-0.7.3.tar.gz | 10.0 kB | Without provenance | Details for nagios_historian-0.7.3.tar.gz |
Release files / nagios_historian-0.7.3.tar.gz
| Download URL | nagios_historian-0.7.3.tar.gz |
|---|---|
| Size | 10.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0204181ff117d1103da0bdfe168255ff5c61b964f73a2454d218a4e5b913c0f9
|
|
BLAKE2b-256 checksum How to use checksums |
6dec708d37be6d756c2ca8dc94641e2e5a40a4a464baafd5433b094aa451e0c1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.0.0 CPython/3.11.0
|
Security for nagios-historian 0.7.3
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.