Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/penguineer/grafanascreenshots
Login to a Grafana Dashboard, take a screenshot and send to MQTT topic
https://github.com/penguineer/grafanascreenshots
Last synced: about 1 month ago
JSON representation
Login to a Grafana Dashboard, take a screenshot and send to MQTT topic
- Host: GitHub
- URL: https://github.com/penguineer/grafanascreenshots
- Owner: penguineer
- License: mit
- Created: 2024-01-03T18:45:37.000Z (12 months ago)
- Default Branch: main
- Last Pushed: 2024-01-31T19:31:24.000Z (11 months ago)
- Last Synced: 2024-05-02T02:12:37.494Z (8 months ago)
- Language: Python
- Homepage: https://hub.docker.com/r/mrtux/grafana-screenshot
- Size: 6.84 KB
- Stars: 0
- Watchers: 1
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- Funding: .github/FUNDING.yml
- License: LICENSE.txt
Awesome Lists containing this project
README
# Grafana Screenshots
> Login to a Grafana Dashboard, take a screenshot and send to MQTT topic
## Configuration
Configuration is done using environment variables:
* `MQTT_BROKER_URL`: The URL of the MQTT broker.
* `MQTT_TOPIC`: The MQTT topic to publish the screenshot data to.
* `GRAFANA_DASHBOARD_URL`: The URL of the Grafana dashboard to capture screenshots from.
* `GRAFANA_USERNAME`: The username to log in to the Grafana dashboard.
* `GRAFANA_PASSWORD`: The password to log in to the Grafana dashboard.
* `WINDOW_WIDTH`: The width of the browser window for capturing screenshots. Default is '1280'.
* `WINDOW_HEIGHT`: The height of the browser window for capturing screenshots. Default is '1024'.These environment variables can be set in your system's environment variable settings, or in the script that calls your Python script. For local development, you can also set these variables in a `.env` file and use a tool like `python-dotenv` to load them.
## Maintainers
* Stefan Haun ([@penguineer](https://github.com/penguineer))
## Contributing
PRs are welcome!
If possible, please stick to the following guidelines:
* Keep PRs reasonably small and their scope limited to a feature or module within the code.
* If a large change is planned, it is best to open a feature request issue first, then link subsequent PRs to this issue, so that the PRs move the code towards the intended feature.## License
[MIT](LICENSE.txt) © 2024 Stefan Haun and contributors