This is an automated email from the ASF dual-hosted git repository.

poorejc pushed a commit to branch FLAGON-344
in repository https://gitbox.apache.org/repos/asf/incubator-flagon.git


The following commit(s) were added to refs/heads/FLAGON-344 by this push:
     new 784046c  [FLAGON-379] completed scaling guide
784046c is described below

commit 784046ce32e97b21dbc64ca0ffd322fb1ac83f0d
Author: poorejc <[email protected]>
AuthorDate: Sat Apr 27 22:05:32 2019 -0400

    [FLAGON-379] completed scaling guide
---
 site/_docs/stack/scaling.md | 44 +++++++++++++++++++++++++++++++++++++++-----
 1 file changed, 39 insertions(+), 5 deletions(-)

diff --git a/site/_docs/stack/scaling.md b/site/_docs/stack/scaling.md
index e7405bd..f66ef2e 100644
--- a/site/_docs/stack/scaling.md
+++ b/site/_docs/stack/scaling.md
@@ -30,11 +30,42 @@ When thinking about how to scale your Apache Flagon Elastic 
stack, it's importan
 
 1. Given that documents are the atomic unit of storage in Elastic, *document 
generation rate* is the most important consideration to scaling. Default 
[Apache UserALE.js parameters]({{ '/docs/useralejs' | prepend: site.baseurl }}) 
produce a lot of [data]({{ '/docs/useralejs/dataschema' | prepend: site.baseurl 
}}), even from single users in Apache UserALE.js. In fact, we used say that 
"drinking from the fire-hose" didn't quite do our data-rate justice--we used to 
say that opening up UserAL [...]
 
-    ![alt text][logBreakdown]
-
-1. Your Elastic resource needs will also grow with *document length*, 
especially the length of 
[strings](https://blog.appdynamics.com/product/estimating-costs-of-storing-documents-in-elasticsearch/)
 within your logs (see also [Elastic's tips on indexing 
strings](https://www.elastic.co/guide/en/elasticsearch/reference/5.5/tune-for-disk-usage.html#_use_literal_best_compression_literal)).
 One of the discriminating features of Apache UserALE.js is its precision--its 
ability to capture both t [...]
-
-    ![alt text][verboseLogs]
+1. Your Elastic resource needs will also grow with *document length*, 
especially the length of 
[strings](https://blog.appdynamics.com/product/estimating-costs-of-storing-documents-in-elasticsearch/)
 within your logs (see also [Elastic's tips on indexing 
strings](https://www.elastic.co/guide/en/elasticsearch/reference/5.5/tune-for-disk-usage.html#_use_literal_best_compression_literal)).
 One of the discriminating features of Apache UserALE.js is its precision--its 
ability to capture both t [...]
+    ```shell
+    ...
+        "pageTitle": "Discover - Kibana",
+        "toolName": "test_app",
+        "userId": "nobody",
+        "type": "click",
+        "target": "a.kuiButton kuiButton--small kuiButton--secondary",
+        "path": [
+          "a.kuiButton kuiButton--small kuiButton--secondary",
+          "div.kbnDocTableDetails__actions",
+          "td",
+          "tr",
+          "tbody",
+          "table.kbn-table table",
+          "div.kbnDocTable__container",
+          "doc-table",
+          "section.dscTable",
+          "div.dscResults",
+          "div.dscWrapper__content",
+          "div.dscWrapper col-md-10",
+          "div.row",
+          "main.container-fluid",
+          "discover-app.app-container",
+          "div.application tab-discover",
+          "div.app-wrapper-panel",
+          "div.app-wrapper",
+          "div.content",
+          "div#kibana-body",
+          "body#kibana-app.coreSystemRootDomElement",
+          "html",
+          "#document",
+          "Window"
+        ...
+    ```
+   
 
 1. Apache Flagon is built to scale as a platform, allowing you to connect 
additional services to your platform that consume user behavioral data. When 
considering scale, the *number of services* you connect to your Apache Flagon 
platform will affect your Elastic stacks' performance. Any production-level 
deployment will require, at minimum a simple three-node [Elastic 
cluster](https://dzone.com/articles/elasticsearch-tutorial-creating-an-elasticsearch-c)
 (with one load-balancing node). As [...]
 
@@ -240,3 +271,6 @@ Benchmarking and adjusting your data-rate so that you can 
scale how you want to
              
 Subscribe to our [dev list]([email protected]) and 
join the conversation!
 
+[mouseOverBench1]: 
https://github.com/apache/incubator-flagon/tree/FLAGON-344/site/_site/images/_site/images/mouseOverBench1.png
 "Proportion of Mouseovers (Benchmark 1)"
+[mouseOverBench2]: 
https://github.com/apache/incubator-flagon/tree/FLAGON-344/site/_site/images/_site/images/mouseOverBench2.png
 "Proportion of Mouseovers (Benchmark 2)"
+[metricBeat]: 
https://github.com/apache/incubator-flagon/tree/FLAGON-344/site/_site/images/_site/images/metricBeat.png
 "Metricbeat Dashboard"
\ No newline at end of file

Reply via email to