Today I’m going to walk you through the steps to enable the monitoring of Ansible with Logscape 3, this may become a series of the steps taken to develop an Ansible app, but let’s start with the basics, configuring your Ansible installation to generate logs, and configuring Logscape to ingest those logs. Continue reading
Logscape 2.5.1 brings a new exciting feature to Logscape which will allow you to build Data Driven Workspaces. Your workspaces can now be designed to provide a logical flow between different views of your data.
Deploying Logscape in the cloud has its challenges. Logscape is a cpu and i/o intensive application and finding an optimal configuration between disk, i/o and cost requires extensive benchmarking and tests.
Recently we started looking at Amazon. We have now have three stages to our benchmarking.
In preparation for release Logscape as a SAAS solution, the Collectd App has been updated. The CollectdApp is one of the first apps to support Logcape Cloud.
- write_graphite – This release now uses the graphite plugin to import collectd metrics.
- Workspaces Update – the workspaces have all been updated
- Zip – The app is now available as a zip. Whereas before it was distributed as a config file.
1.New UI changes download here (build id: 2010 )
The Search page has had a few subtle changes to help you navigate and explore your data. A new data sources is now available. When you arrive on the search page for the first time or click ‘New Search’ you will see a list of data sources available in your environment which you can click on to search.
Check out the new MySQLApp. Monitor the health of your MySQL instances and servers.
Download the MySQLApp here
Features to look forward to.
- Resource KPIs such as memory, disk I/O and server load.
- Innodb statistics
- Query Cache Trends
- Network – bandwidth utilization
- Threads Created vs Threads Cached.
Subscribe to our mailing list click here
Monitoring Docker – Part II
The docker landscape is advancing at a rapid pace but the state of docker monitoring is still in its infancy. Most docker monitoring solutions out there will give you basic resource monitoring of your containers. They will tell you how much mem, cpu and disk they are using at a container level. This useful but it its utility diminishes as our deployment gets larger In the second part of the docker series I am going to a look at what other attributes we can use to make docker monitoring more useful.
In this blog post I will show you how to use the JavaApp to monitor application servers like Tomcat, JBoss and FUSE.
We’ll start off with Tomcat, since it is fairly easy to set up.
Before we get started, let’s take a look at the steps.
- Select Tomcat JMX Attributes.
- Download and Configure the JavaApp
- Create a Custom Data Collection Service
- Start Monitoring
Docker has been around for roughly a year, it was open-sourced by the guys at dotCloud ( the PAAS provider) and has since caused a revolution in the devops community. It has the backing of industry heavy weights such as Google, Rackspace and Redhat . In this blog post, I will attempt to give an initial look at monitoring docker, with a specific focus on system health. The technology stack under Docker is a large topic so I will not be going into much detail on setting up a docker environment. Before we dig right in let’s find out a bit about docker.