![]() ![]() Run the script in a scheduled task to push the data to Geckoboard.Write a PowerShell script that uses the query from step 3, and then posts the data to the widget.See this blog post for how I normally do it. Work out the SQL query that you need to extract the data.Make sure you set its method to Push, and grab the Push URL and Widget key whilst you’re at it. The documentation for each widget describes how the JSON data should look. NET 4.5 & WMF 4.0, and the SQLite PowerShell Provider. ![]() The prerequisites for this are the same as in the previous blog post about Spiceworks and data extraction. The rest was just a matter of wiring together the right queries to extract the data that I wanted to monitor. I’d already worked on getting data out of Spiceworks using PowerShell for my email reports, so I had that part of it covered also. The Geckoboard Push API uses JSON, which is easy to work with in PowerShell. The other thing with a webservice is that it’s usually run with compiled code, which isn’t as flexible to maintain or for other team members to pick up. What sold it for me was the fact that Geckoboard have a Push API that would allow me to push data to the dashboard widgets, thus avoiding the need to create some sort of webservice that I have to open ports on the firewall to. I’d seen Geckoboard around, and decided to have a look into it. So, we needed a better way to keep an eye on our Spiceworks helpdesk tickets.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |