eventgen reboot

TA-nmon/default/eventgen.conf

@@ -1,10 +1,14 @@
 # eventgen.conf
 
 # The eventgen samples come from real system running in the IBM Power development plateform (PPD)
-# These are key value invents from the TA-nmon-hec
+# performance data is generated in key value format via the TA-nmon-hec
+
+# We provide 2 AIX servers and 2 Linux servers, 1 of each type runs  in CPU usage anomaly due to a load stress tool
 
 # Deploy the Splunk eventgen from https://github.com/splunk/eventgen under $SPLUNK_HOME/etc/apps/SA-Eventgen
-# Create an index called "nmon" and restart Splunk
+# Create an index called "nmon" and restart Splunk, data will immediately start to be available automatically
+
+# Notes: Only performance and configuration data will be available
 
 [nmon_performance_sample]
 count = 100

TA-nmon/default/props.conf

@@ -701,14 +701,12 @@ TRANSFORMS-cleandata_fromsyslog = nmon_clean_fromsyslog_rewrite
 #			SPLUNK HEC (HTTP INPUT)
 ##############################################
 
-# It is possible to forward nmon data over HTTP using the nmon-logger-hec package
+# It is possible to forward nmon data over HTTP using the TA-nmon-hec and nmon-logger-hec packages
 
-# the package is available at: https://github.com/guilhemmarchand/nmon-logger
+# TA-nmon-hec: the package is availanle at: https://splunkbase.splunk.com/app/3668
+# nmon-logger: the package is available at: https://github.com/guilhemmarchand/nmon-logger
 
-# In this scenario, the nmon-logger is deployed on servers, it produces the nmon data and stream directly
-# to your indexers using the Splunk HTTP input
-
-# This is "no Universal Forwarder" deployment scenario, which means the package is totally independent
+# In this scenario, the data and is streamed directly to the HEC input
 
 ### nmon_data ###