Operations | Monitoring | ITSM | DevOps | Cloud

%term

Minimize Risk with Continuous Integration (CI) and Deployment (CD)

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.

Unearth new repositories and Git v2 improvements in Bitbucket Server 5.13

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.

How to Monitor JavaEE Applications' EJB Method Performance on WebLogic?

WLSDM has back-end dashboards that offers monitoring EJB container. On WLSDM EJB dashboard you are able to view EJB Business Methods, its applications and method duration... etc. You can set alarm and configure EJB method duration threshold in "Monitoring & Diagnostics" page. You will be notified if EJB performance duration exceeds the threshold that you have defined.

Seven discernible stages in taking a solo startup from beta to GA

Last week the “beta” tag officially came off of Checkly ! I bumped into many things in the period between launching a private beta and hammering down on all features and ripping the beta notice of the nav.navbar. In this post, I tried to funnel a bunch of these learnings into a somewhat logical order, as they felled like hoops I had to jump through to get to the next hoop.

How to Troubleshoot PHP Web Application Problems

Not all problems or issues in web development can be detected during development or testing. There are even web application errors that are hard to catch like runtime errors. Most PHP developers or server administrators will just look at the web server or database logs once an issue arises. They would just grep the logs for errors or timestamps in which the error occurred. This method of troubleshooting PHP problems requires a high technical skill and would take a long time to find the root cause.