
Security News
vlt Launches "reproduce": A New Tool Challenging the Limits of Package Provenance
vlt's new "reproduce" tool verifies npm packages against their source code, outperforming traditional provenance adoption in the JavaScript ecosystem.
bloomsky-prometheus-exporter
Advanced tools
Prometheus exporter that expose Bloomsky weather data.
The stations are identified by their ID and name.
Get your personnal key at http://dashboard.bloomsky.com/
Clone the repo, or install it on your system with npm:
npm install -g bloomsky-prometheus-exporter
Usage: bloomsky-exporter [config file] {OPTIONS}
Standard Options:
--port, -p Select port for the metric server
default 9262
--key, -k Your Bloomsky api key
Get it on http://dashboard.bloomsky.com/
--unit, -u Set to "intl" if you prefer international units, "impl" for imperial
Default to imperial units
--endpoint, -e Optional parameter to override the bloomsky api endpoint.
--help, -h Show this message
Example (see below for bloomsky.yml config file):
bloomsky-exporter bloomsky.yml
Exemple:
var getMetrics = require('./index.js')
getMetrics({
key: 'Your Key',
unit: 'intl'
}, function(err, metrics) {
console.log(metrics)
})
You can use command line options, a yaml file or environment variables.
Options available are key
, port
, unit
and eventually the Bloomsky API endpoint
.
The only mandatory option is key, others have default values.
Priority is command line args
> yaml
> env vars
.
Minimal yml file:
key: <yourkey>
unit: intl
You can define them in a .env file
BLOOMSKY_KEY=<yourkey>
BLOOMSKY_PORT=<port>
BLOOMSKY_UNIT=<intl|impl>
BLOOMSKY_ENDPOINT=<endpoint>
Build (or wait for docker hub entry...)
docker build -t "krazylek/bloomsky-prometheus-exporter" https://github.com/krazylek/bloomsky-prometheus-exporter.git
Run
docker run -d -v $(pwd)/bloomsky.yml:/mnt/bloomsky.yml -p 9262:9262 --name bloomsky krazylek/bloomsky-prometheus-exporter
I am not affiliated with Bloomsky Inc in any way, and it is only a hobby project meant for personal use.
FAQs
Bloomsky API exporter for prometheus timeseries db
The npm package bloomsky-prometheus-exporter receives a total of 0 weekly downloads. As such, bloomsky-prometheus-exporter popularity was classified as not popular.
We found that bloomsky-prometheus-exporter demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
vlt's new "reproduce" tool verifies npm packages against their source code, outperforming traditional provenance adoption in the JavaScript ecosystem.
Research
Security News
Socket researchers uncovered a malicious PyPI package exploiting Deezer’s API to enable coordinated music piracy through API abuse and C2 server control.
Research
The Socket Research Team discovered a malicious npm package, '@ton-wallet/create', stealing cryptocurrency wallet keys from developers and users in the TON ecosystem.