Logscape Upgrade Guide for Version 2.2

As part of 2.2 we have developed the Logscape Monitoring App and rolled into it the default DataSources (plus a new one). We also managed to remove a bunch of redundant datasources and tidy things up. We have now carried out the upgrade on several environments.

One environment has 120 Indexers and performs at about 100,000,000 events per second (wow!).


The following steps are similar to a standard upgrade but with a few quirks. Have a read of the following page.
Continue reading

Logscape 2.2 is now available for download

See the release notes for ticket information

LogManagement Dashboards just got more flexible 😉

We have added several UI niceties and also included a packaged Logscape-monitor app (included in the downloads folder). I’ll walk you through each of these.

1. Workspace level filtering

How many times have you looked at a Workspace (dashboard) and thought – ‘wow – there are just too many lines and it looks like a pile of spaghetti’. I just want to see this ‘process’ or this servers information. Now you can.

Workspace-level filters are an interactive filter on the chart legend items and table elements. Data is viewed that matches the text entered (multiple entries are supported using a comma). In the example, the WindowsApp we are viewing processes from across several servers- we filter the workspace to restrict data the Wmi processes.



2. Logscape Monitoring App

We have now leveraged the list of auditing built into the system runtime [work/vsaudit,events, audit, logger.stats]. Note, this approach relies exclusively on discovered fields (and was pretty easy to put together).  It includes 5 screens. Data Audit, User Activity, System performance, Alerting as well as the underlying VScape service status.

Note: You can deploy the logscape/downloads/logscape-monitor.config file containing the Workspaces and DataSource configuration on the Deployment page. Upload the config file and click deploy to install and make it available.




Alert: audit-alerts

3. Deploy config files via the deployment page



4. Export configuration elements using a type specifier:

Using Workspace, Search, DataType, DataSource and Alert qualifiers.

i.e. deployment-export