Comments
-
Does 'Java Monitoring' mean JMX? Very cool if so!
-
We've used MS SQL Reporting Services to cover both executive/summary type of reporting generated & sent via email on a schedule as well as graphs inserted into Orion dashboards (via CustomHTML resource). Since Reporting Services is included in MS SQL 2005/2008 the only cost is someones time to build reports and such.
-
If you have little/no experience running MS SQL servers and you are going to be the one responsible for its care and feeding (a good base level of understanding is better than looking at it as a black box/magic): * Maintaining a Microsoft SQL Server 2005 Database * Implementing a Microsoft SQL Server 2005 Database If…
-
Are there any updates on the status of these changes (#1, #3 and #6 specifically)? Thanks
-
If you are not planning on doing transaction log backups (in order to be able to restore your database to a point in time other than when it was last backed up, and if you are not maintaining a log-shipped standby copy) change the Recovery Model on the database to Simple. This will truncate transactions from the Tlog as…
-
I would recommend using MS SQL Reporting Services, sourcing from the Orion SQL database and scheduling report delivery using 'Subscriptions' (basically just SQL schedule jobs but with a nicer UI). We've found Reporting Services to be a very effective supplement to Orion graphing/charting/reporting.
-
Most definitely!
-
Rather than having your perl script parse the page and trap on it why not plug the parsing scripting into an APM 'Windows Script' component and have it return statistic directly into Orion? I have something similar set up which we are using in combination with a JMX 2 HTTP gateway service that we wrote to poll JMX data…