In my ever onward quest to show to the world how easy it is to get up and started with Logscape, today I’m going to use a Logscape docker container in order to build visualisations based off some publicly available CSV files in no time at all. If you’ve never used the Logscape docker image, then check out my previous blog.
Logscape 3.2 introduced native JSON support, meaning that when working with JSON data there’s no need for datatypes, instead Logscape automatically pulls the keys from your structure.
This removes the sometimes daunting configuration step, and instead lets you get straight down to business with visualising your data. With that in mind, today we’re going to be embracing our inner geek, and get to work visualising some JSON from the game EvE Online™.
Logscape version 3.2 is now available for public download, you can get it now from the Logscape Website.
A brief rundown of Logscape 3.2 brings with it, and what we’re going to cover today…
- File Explorer
- JSON Support (Including JSON Arrays)
- Failover Overhaul
- Performance and Stability Changes
Logscape Analytics’ are incredibly powerful, however, are you using them to their full potential? In this blog post we’re going to go over some of the less used analytics, show you how to use them, and hopefully inspire you to use your Logscape instance in new and exciting ways. So, without further ado let’s get into some searches. Continue reading
The long awaited version 3 update to Logscape is finally here.
In version 3 we welcome multiple new and exciting features. We’ve improved search performance, zoning and the search UI as well as a series of bug fixes. Version 3 is sure to surprise even the most experienced user. This release is bigger, better and faster! If you want to find out all you need to know about these excellent new features, and how this update will affect you, read on.
If you just want to get started, download it for free right now from our Website.
If you’ve already tried it, why not tell us what you think? We’d love to hear your feedback. Simply message us and let us know.
Docker 1.5 came out a few weeks ago and with it the new stats api arrived. Before 1.5 there was no standard way to collect the metrics of running docker containers without writing custom scripts to parse files stored in the proc memory file system.
Sitting at my desk, I was approached and asked this question.
Do you guys support Platform Symphony?
An interesting question, really we “support” most anything, Logscape has the base functionality for most tasks, and product “apps” just build upon that functionality, the app provides the workspaces, data types and sources, as well as the tools that Logscape will use to find the data you want. But at the end of the day it’s still Logscape, just it’s running a groovy script to fetch your metrics.
So what is the process that goes into making a Logscape App?
Release 2.5.1 includes enhancements to JMX functionality, improvements to Logscape roll detection aswell as significant search performance optimisation.
2.5.1 Introduces new linking functionality. This allows you to flawlessly link your workspaces and transfer context between them providing a troubleshooting workflow for non-expert users of the Logscape system.
The release notes are here.
After a long test, fix and thrashing cycle 2.3 is finally available!
Head over to the logscape.com to request the download.
To upgrade you can follow the standard upgrade procedure as described here:
After that, the following installation tasks can be followed:
- Install the new Home page. Upload the new logscape/downloads/logscape-home.config and click deploy
- Install the updated Logscape Monitoring app has a couple of minor updates.. Upload the new logscape/downloads/logscape-audit.config and click deploy
- If you wish edit your existing DataSources to include the new System-Fields – edit your datasource and choose the ‘System-Time-Series’ checkbox to include ‘DayOfWeek, Date etc’
The release notes can be found as the usual place.