background preloader

Icinga – Open Source Monitoring

https://www.icinga.org/

Related:  SysAdmin Tools & Resources

Deployment method for ETLA products The Adobe Customization wizard prepares an Acrobat installation folder for installation in a deployed environment. The Acrobat Professional and Standard installation files called be run without customization with this tool and will accept your Acrobat enterprise serial number. You must download the Acrobat installer, Adobe Customization wizard, and serial number on the platform you want to package for installation.

THE SYNC PROJECT We all know the expression. And we think we know what it means. But do we? Write it down: Network security documentation basics I just finished a disaster recovery with a client that really hit home the need to have good network security documentation.... By submitting your email address, you agree to receive emails regarding relevant topic offers from TechTarget and its partners. You can withdraw your consent at any time. Founders Den Space at Founders Den is offered on an invite-only basis to startups referred through the networks of the Founders Den community. Archy is the best file manager for the cloud. founders: Christian Almenar, Marc Cercos, Giuseppe Basile August allows physical environments to respond seamlessly to user behavior. founders: Jason Johnson, Yves Bhar

Types of Documentation Needed by Companies by Ron Kurtus - Succeed in Technical Writing: School for Champions SfC Home > Writing > Technical Writing > by Ron Kurtus (revised 3 May 2003) Every business—large or small—needs documentation to operate effectively. Requirements for extensive internal documentation are spelled out in the ISO 9000 series of international standards. The major classifications of needed documents include marketing, user guides, administrative material and published works. Technical communicators are needed to write each of these types of documents.

The 8 Types of Technical Documentation and Why Each Is Important Technical documentation is critical to the success of any software. However, most creators of software struggle to provide adequate documentation for their product. Rare is the software that is praised for its documentation. When documentation is praised, it is often only praised for having some documentation, which is more than most, but in reality documentation is usually still inadequate. So what constitutes adequate documentation? IT Documents and Policy Templates Documents listed here are free to download and employ as a template in your own organisation. IT Acceptable Use Policy A model policy for you to copy and adapt to the needs of your organisation. Sections shown as <yourorg> are intended to be replaced by the name of your own organisation (multiple find and replace).

Five areas of documentation that need continuous monitoring (The Invisible Thread) When I first started working on DevOps-related software, continuous monitoring didn't sound like something that was big enough to be one of the pillars of a new software methodology. My dev-centric background was part of why I discounted monitoring, but I also figured that if we were already automating things like deployment and testing, wouldn't the tools already record things like test results? Big deal! The most popular thing I've yet written is a series of articles on reporting with Rational Team Concert and Eclipse Business Information and Reporting Tools, and yet I still figured that reporting was something done manually and as needed, not constantly.

Related: