Merge pull request #41 from guilhemmarchand/readme_update_24112019

readme update

README.md

@@ -4,12 +4,15 @@
 | ---    | ---          |
 | master | [![master status](https://circleci.com/gh/guilhemmarchand/trackme/tree/master.svg?style=svg)](https://circleci.com/gh/guilhemmarchand/trackme/tree/master)
 
-## The Splunk TrackMe application for data source monitoring provides a handy user interface and workflow for Splunk administrators to monitor the availability of their data sources:
+## The Splunk TrackMe application provides automated monitoring and visibility insight of your data sources availability, with a powerful user interface and workflow for Splunk product owners to detect and alert on failures or abnormal latency:
 
-- Discover and store data sources and hosts information and states
-- Provides a handy and easy user interface to manage states, configuration and quickly trouble shoot alerts
-- Analyse and detect lack of data and performance lagging of data sources and hosts
-- Easy administration via graphical human interface
+- Discover and store key states information of data sources, data hosts and metric hosts availability
+- Provides a powerful user interface to manage activation states, configuration and quickly trouble availability failure detection
+- Analyse and detect lack of data and performance lagging of data sources and hosts within your Splunk deployment
+- Record and investigate historical changes of statuses, as well as administrators changes (audit flipping and changes)
+- Easy administration via graphical human interface from A to Z
+- No matters the purpose of your Splunk deployment, trackMe will easily become an essential and easy piece of your deployment, and even providing efficient answers to PCI and compliance requirements
+- Never let again your team be the last to discover what empty and no results found mean!
 
 ![screenshot](./docs/img/screenshot.png)
 
@@ -27,7 +30,7 @@
 
 Splunk administrators and engineers have to spend a good amount of time and energy to on-board new data sources, another data source after another data source.
 
-However, it is very frequent to realise after math that something when wrong, for some reason the sender stopped sending, an issue appeared, a network rule was lost...
+However, it is very frequent to realise after math that something went wrong, for some reason the sender stopped sending, an upgrade broke a configuration, a network rule was lost…
 
 No administrator should be informed of an issue in the data flow by the customer or end users, this is why you need pro-activity and cost less availability monitoring.
 
@@ -37,4 +40,13 @@ This tiny application provides a handy user interface associated with a simple b
 
 Made by Splunk admins for Splunk admins, the TrackMe application provides builtin powerful features to monitor and administer you data source monitoring the easy way!
 
+## Use case for TrackMe?
+
+No matters the purpose of your Splunk deployment, trackMe will easily become an essential and positive piece of your Splunk journey:
+
+- Security Operation Centers (SOC) with or without Enterprise Security compliance: detect lack of data, abnormal latency potentially impacting your security posture
+- PCI and compliance: deliver, alert and action
+- Monitoring and insight visibility about your indexes, sourcetypes, events and metrics
+- General data activity monitoring and detection of Zombie data
+
 **Please consult the online documentation:** https://trackme.readthedocs.io

docs/index.rst

@@ -40,7 +40,7 @@ Welcome to the Splunk TrackMe application documentation
 
 Splunk administrators and engineers have to spend a good amount of time and energy to on-board new data sources, another data source after another data source.
 
-However, it is very frequent to realise after math that something when wrong, for some reason the sender stopped sending, an issue appeared, a network rule was lost...
+However, it is very frequent to realise after math that something went wrong, for some reason the sender stopped sending, an upgrade broke a configuration, a network rule was lost…
 
 No administrator should be informed of an issue in the data flow by the customer or end users, this is why you need pro-activity and cost less availability monitoring.