Speaker: Pete Zerger and a Dude Who Was WIth Avicode
APM was Avicode, and allows .NET and J2EE application monitoring from the inside. Help IT isolate the issue. Provide the app team with the info they need to fix the app.
Teams you might have involved in app troubleshooting:
- Operations: Runs the infrastructure n a day-day basis
- Support and development: writes it and fixes bug
- QA/Testing: tests it
- DevOps: owns the production code
- Daily/weekly app health analysis
- Fixing top issues
- Next application release scope
- Improve monitoring configuration
Start with Top reports
Figure out how often to send reports, who to send them to, and what apps to include.
Problems distribution analysis is a good high level report of all apps. Application status gives you a week-week report on app performance/health. Run it weekly and send to an active/involved supervisor. Application CPU utilization should be run weekly/monthly.
Make a note of http://dinnernow.codeplex.com/ for testing/demo.
Filter out noise, e.g. non-actionable alerts .. maybe fixed in next release, etc. Use rules everyday. Start with top level problems, create rules for exception events.
Using REGE Sensitive Data Filters
You can use expressions to find and mask sensitive data that you don’t want out in the wild, e.g. social security number, credit card number, etc.
There’s a lot more demo after this. Best you watch the video when it’s made available in a few days.
This blog post is the property of Aidan Finn (@joe_elway / http://www.aidanfinn.com) and may not be reused in any manner without prior consent of Aidan Finn. You may quote one paragraph from this blog post if you link to the original blog post.
No related posts.