Previously on WLSDM blog, we have learned about monitoring applications’ database statements (JDBC SQL) and performance on Oracle WebLogic server. In this blog post we have created another tutorial to learn how to monitor and diagnose WLSDM back-end EJB business method invocation events.
It’s 2:37 a.m. on a Tuesday night, you’re asleep—but it’s also your turn to be on call. You receive a phone call from PagerDuty. Your partner hits you with a pillow in an attempt to wake you up. It worked. You groggily answer the call and hear your favorite robo-guy on the other end of the line.
Nobody knows your services/infra better than you, not even Honeycomb. If there’s one maxim for Honeycomb, it’s that context is king. Context determines the questions you can ask. The only way to make complex systems truly tractable is to make all questions possible. Ergo: more context. Context everywhere. Context coming out of the walls. You should be awash in context.
This is the first in a series on server monitoring. The primary focus of these posts is monitoring in a *nix environment. Monitoring servers is important. Whether it be finding an issue in a test environment prior to deploying or debugging an issue in production, we need access to information on our server to be able to tease apart what went wrong.
OpsGenie is pleased to announce an enhanced integration with Zendesk, building off of our existing bidirectional integration to now support incidents.
Ahoy there. Continuous shipping: a concept many companies talk about but never get around to implementing. In the first post of this three-part series, we discussed the use case for continuous shipping. Let’s move on to part two: the integration and deployment stages of the continuous shipping process. Part three will wrap up the series with a look at the monitoring and feedback phases. All aboard that’s coming aboard.
How much time do you spend every week trying to find things? At home, it’s finding your keys and, at work, it’s finding the root cause of a bug or an old pull requests that introduced the bug. Since we’re not in the business of tracking your keys, Bitbucket Server 5.13 is making it easier to discover repositories and find pull requests tied to a given commit. You can also enjoy support for Git v2, with faster no-op fetches.
Citrix Director is a web-based monitoring console for Citrix XenApp and XenDesktop virtualization platforms that allows administrators to control and monitor virtual applications and desktops. Starting with version 7, Citrix Director is the default management tool, replacing the erstwhile Citrix EdgeSight.
Today we’ve introduced an overhaul of our reporting tool which will make it much easier to get the exact data you want sent out to the people who need to see it. Previously it was only possible to send an automatic report for all uptime tests in your StatusCake account.
