Add azure module doc #9510

karenzone · 2018-05-02T14:31:23Z

Rework of unreleased Azure module content after redesign

karenzone · 2018-05-17T15:59:56Z

@acchen97 @jakelandis Not ready for review, but I want to get your input on content and direction.
Jake, when we last spoke, you had some ideas for reworking your implementation that might change the docs.
I'm concerned about the squishiness between helping a user do a quick demo and deploying in a production environment. I'm sure I oversimplified by adding a Deployment section at the end, but wanted to get the conversation started.
Shall I set up some time for the three of us to discuss?

acchen97 · 2018-07-07T03:49:00Z

docs/static/azure-module.asciidoc

+=== Azure Module  [Experimental]
+experimental[]
+
+The https://azure.microsoft.com/en-us/overview/what-is-azure/[Microsoft Azure] module in Logstash helps you easily integrate your Azure


Can we put some more detail on what the module does? Maybe something like the below...

"The Logstash Azure module enables you to easily monitor your Azure cloud environments and SQL DB deployments with deep operational insights across multiple Azure subscriptions. Explore the health of your infrastructure in real-time to accelerate root cause analysis and decrease overall time to resolution.

Analyze infrastructure changes and authorization activity

Identify suspicious behaviors and potential malicious actors

Perform root-cause analysis by investigating user activity

Monitor and optimize your SQL DB deployments"

acchen97 · 2018-07-07T03:51:54Z

docs/static/azure-module.asciidoc

+
+
+[[azure-prereqs]]
+==== Prerequisites


We also need to add or link to instructions for setting up Azure Monitor on the Azure side. Azure Monitor centralizes the logs to an Event Hub which we ingest from.

https://docs.microsoft.com/en-us/azure/monitoring-and-diagnostics/monitoring-overview-azure-monitor

Specifically: https://docs.microsoft.com/en-us/azure/monitoring-and-diagnostics/monitoring-stream-activity-logs-event-hubs and https://docs.microsoft.com/en-us/azure/sql-database/sql-database-metrics-diag-logging for how to setup on Azure side of things. "Stream to an event hub" option for the latter.

acchen97 · 2018-07-07T03:52:59Z

docs/static/azure-module.asciidoc

+suite of {kib} dashboards to help you start exploring your data immediately.   
+
+[[azure-dashboards]]
+==== Dashboards


Good stuff here!

acchen97 · 2018-07-07T04:42:47Z

docs/static/azure-module.asciidoc

+
+These {kib} dashboards are available and ready for you to use. 
+
+* *Overview*. Top-level view into your Azure operations, including info about users, resource groups, service health, access, activities, and alerts. 


Should we group these into two logical sections?

"Infrastructure Activity Monitoring" - Overview, User Activity, and Alerts

"SQL DB Monitoring" - SQL DB Overview, SQL DB Database View, SQL DB Queries

acchen97 · 2018-07-07T06:12:45Z

I like the direction, left a few comments. Happy to discuss live if you'd like.

jakelandis · 2018-07-09T14:25:15Z

docs/static/azure-module.asciidoc

+To get started with the Azure module:
+
+ . Install the {logstash-ref}/plugins-inputs-azure_event_hubs.html[azure_event_hubs
+ plugin]. 


no need to install plugin. it is a default plugin as of 6.4

jakelandis · 2018-07-09T14:25:40Z

docs/static/azure-module.asciidoc

+
+["source","shell"]
+-----
+bin/logstash-plugin install logstash_input_azure_event_hubs


no need to install plugin

jakelandis · 2018-07-09T14:26:12Z

docs/static/azure-module.asciidoc

+[[azure-module-setup]]
+===== Set up the module
+
+TBD: From the LS directory?


jakelandis · 2018-07-09T14:33:12Z

docs/static/azure-module.asciidoc

+You can specify <<azure_config_options, options>> for the Logstash Azure module in the
+`logstash.yml` configuration file or with overrides through the command line. 
+
+The azure_event_hubs plugin and the Azure module support two configuration


there are really 3 configuration modes, command line, basic, and advanced.

command line = 1 event hub
basic = multiple event hubs same config
advanced = multiple event hubs different config

I think it makes sense to document it this way instead of the 2 ways with the caveat that basic has two ways (command line vs. yml) and the command line only supports a single event hub.

jakelandis · 2018-07-09T14:37:17Z

docs/static/azure-module.asciidoc

+`event_hub_connection`.
+
+[id="plugins-{type}s-{plugin}-config_mode"]
+===== `config_mode`


the config mode is chosen automatically based on the yaml, no need to document here.

jakelandis · 2018-07-09T14:40:35Z

docs/static/azure-module.asciidoc

+
+[source,ruby]
+----
+azure_event_hubs {


we should avoid using the plugin examples. the module maps the yaml configuration to the plugin configuration. I think the descriptions (for the most part) apply, but the examples, if any provided, should be in the yaml style.
For example:

var.input.azure_event_hubs.event_hubs: - ["name", "event_hub_connection", "storage_connection", "initial_position", "decorate_events"] - ["insights-operational-logs", "Endpoint=sb://example1...", "DefaultEndpointsProtocol=https;AccountName=example1....", "HEAD", "true"] - ["insights-metrics-pt1m", "Endpoint=sb://example2...", "DefaultEndpointsProtocol=https;AccountName=example2....", "TAIL", "true"]

@jakelandis Gotcha.
WRT: "the examples, if any provided..."

Before I do a lot of unnecessary reformatting, let's decide if we need the examples at all. If we need just a few examples, I'll focus on reworking those.

maybe we can provide a an example of how to map the input the options to yaml, and then hyperlink each of the options to the input documentation. Maybe just a bullet list of the linked options ?

jakelandis · 2018-07-09T14:45:56Z

docs/static/azure-module.asciidoc

+[[run-azure]]
+==== Start the module 
+
+Run this command from the Logstash install directory:


Run this command from the Logstash install directory (with the logstash.yml properly configured) ?? ...or something like that.

@jakelandis These are fantastic comments, and the updates are going well. Link ^^ isn't working for me. Can you point me in the right direction, please?

NM. I think I know what you're getting at.

jakelandis · 2018-07-09T14:47:00Z

docs/static/azure-module.asciidoc

+
+Many of the logs contain a "properties" top level field. This is often where the
+most interesting data lives. There is not a fixed schema between log types for
+properties fields coming from different sources. This can cause mapping errors


This can cause mapping errors ...

Can we nuke that sentence ? We cover it later with "To avoid mapping errors, ..."

jakelandis · 2018-07-09T14:49:01Z

docs/static/azure-module.asciidoc

+
+
+
+==== Testing


let's leave this section out entirely ... i think it makes for the readme, but not the ascii doc.

karenzone · 2018-07-17T16:00:01Z

@jakelandis @acchen97 Ready for another look.
@dedemorton FYI - I always appreciate your insights and comments if you have time to look.

dedemorton

Just did a quick scan. Nice work. Added a few comments about some of the asciidoc coding.

dedemorton · 2018-07-17T22:21:00Z

docs/static/azure-module.asciidoc

+`event-hub-connections`. The the advanced configuration uses `event_hubs` and
+`event_hub_connection`.
+
+[id="plugins-{type}s-{plugin}-event_hubs"]


You shouldn't use the type and plugin attributes here. This convention is used in the plugin docs only. The attributes get set for each topic in the plugin docs and don't exist in the other parts of the Logstash Reference. The book probably builds without errors right now because the build ignores unresolved attributes 😱. However, if someone references this ID, the link will break. Use [[event_hubs]] instead, and make sure you change the other IDs in this topic. I'm guessing you must have copied this over from some plugin docs. :-) Easy mistake....

dedemorton · 2018-07-17T22:23:41Z

docs/static/azure-module.asciidoc

+
+[cols="<,<,<",options="header",]
+|=======================================================================
+|Name |Description|Notes


Tables can render strangely in our docs right now if there are long words (dotted names are often that problem) that result in text overrunning the navigation widget. Generally we try to avoid using complex tables (with more than two columns). At this point, I'd just check the output to see if there are overruns and use a different format strategy (maybe definition lists) if there are issues.

Looks good on local build. Will verify again.

dedemorton · 2018-07-17T22:25:25Z

docs/static/azure-module.asciidoc

+
+Microsoft is the best source for the most up-to-date Azure information. 
+
+* [Overview of Azure Monitor]https://docs.microsoft.com/en-us/azure/monitoring-and-diagnostics/monitoring-overview-azure-monitor


This is markdown, not asciidoc formatting. Ditto for the other items in this list.

Doh! Is this correct?
https://docs.microsoft.com/en-us/azure/monitoring-and-diagnostics/monitoring-overview-azure-monitor[Overview of Azure Monitor]

Looks right to me! Using the wrong link format is a common mistake for the dev team because they have to switch between markdown and asciidoc all the time.

dedemorton · 2018-07-17T22:29:01Z

docs/static/azure-module.asciidoc

+
+Connection string that identifies the Event Hub to be read. Advanced
+configuration options can be set per Event Hub. This option modifies
+`event_hub_name`, and should be nested under it. (See sample.) This option


I'm just skimming for issues, but it seems like "See sample" is an incomplete sentence and perhaps needs a link

dedemorton · 2018-07-17T22:29:46Z

docs/static/azure-module.asciidoc

+* Value type is <<boolean,boolean>>
+* Default value is `false`
+
+Adds metadata about the Event Hub, including Event Hub name, consumer_group,


Should these be formatted in backticks? If not, maybe change this to say consumer group, processor host, and so on (without underscores).

dedemorton · 2018-07-17T22:31:03Z

docs/static/azure-module.asciidoc

+properties fields coming from different sources. 
+
+For example, one log may have
+properties.type where one log sets this a String type and another sets this an


usually we format field names in backticks.

jakelandis · 2018-07-18T13:25:25Z

docs/static/azure-module.asciidoc

+      - ["insights-operational-logs", "Endpoint=sb://example4...", "DefaultEndpointsProtocol=https;AccountName=example4....", "HEAD",             "true"]
+-----
+
+===== Map input options to the logstash.yml file


I think we leave out this section entirely, the examples above should be sufficient.

jakelandis · 2018-07-18T13:27:06Z

docs/static/azure-module.asciidoc

+===== `event_hubs`
+* Value type is <<array,array>>
+* No default value
+* Ignored for basic configuration


nit: Ignored for basic and command line configuration.

jakelandis · 2018-07-18T13:28:36Z

docs/static/azure-module.asciidoc

+* Ignored for basic configuration
+* Required for advanced configuration 
+
+Defines the Event Hubs to be read. An array of hashes where each entry is a


This is slightly different for the yaml...

How about:

Defines the per Event Hubs configuration for the advanced configuration (<- link to above).

jakelandis · 2018-07-18T13:29:32Z

docs/static/azure-module.asciidoc

+===== `event_hub_connections`
+* Value type is <<array,array>>
+* No default value
+* Required for basic configuration


nit: Required for basic and command line configuration
and * Ignored for advanced configuration.

jakelandis · 2018-07-18T13:31:53Z

docs/static/azure-module.asciidoc

+List of connection strings that identifies the Event Hubs to be read. Connection
+strings include the EntityPath for the Event Hub. 
+
+The `event_hub_connections` option is defined


I think we can remove this sentence.

edit: both sentences, actually.

jakelandis · 2018-07-18T13:36:28Z

docs/static/azure-module.asciidoc

+
+
+[id="plugins-{type}s-{plugin}-event_hub_connection"]
+===== `event_hub_connection`


This is a bit tricky... and we may want to deviate from the plugin doc a bit here.

I would suggest to remove this section entirely, and take the note on line 208 and put it (or make a new similar one) under 'event_hubs' . I think that will sufficiently document this options.

Since we are de-emphasizing the advanced config, and for YAML this only appears in the table name row (not a top level config option like in the plugin), it feels better to leave this out.

jakelandis · 2018-07-18T13:40:07Z

docs/static/azure-module.asciidoc

+* [Azure SQL Database metrics and diagnostics logging]https://docs.microsoft.com/en-us/azure/sql-database/sql-database-metrics-diag-logging
+* [Stream the Azure Activity Log to Event Hubs]https://docs.microsoft.com/en-us/azure/monitoring-and-diagnostics/monitoring-stream-activity-logs-event-hubs 
+
+


Do we want to include a best practice section like here: https://github.com/logstash-plugins/logstash-input-azure_event_hubs/blob/master/docs/index.asciidoc#best-practices ?

jakelandis · 2018-07-18T13:46:03Z

docs/static/azure-module.asciidoc

+-----
+
+[[azure_config_options]]
+===== Configuration options


Can we add a quick blurb about prefixing the configuration options ? With an example or two?

For example:
threads configuration
Command line:

-M "azure.var.input.azure_event_hubs.threads=8"

Basic:

var.input.azure_event_hubs.threads: 8

Advanced:

var.input.azure_event_hubs.event_hubs: - ["name", "event_hub_connection", "threads"] - ["insights-operational-logs", "Endpoint=sb://example1...", 8]

jakelandis · 2018-07-18T13:48:54Z

@karenzone - this is looking really good. I left some comments, please take them as suggestions not must dos.

karenzone · 2018-07-18T21:12:43Z

FYI - I'm still working to resolve the comment about prefixing config option. Wanted to get this back out to review quickly so @acchen97 can see where we are.

@jakelandis WRT #9510 (comment). Please see if I resolved this issue the way you wanted it.

jakelandis · 2018-07-19T15:21:55Z

docs/static/azure-module.asciidoc

+* **Create a {ls} consumer group.** 
+Create a new consumer group specifically for {ls}}. Do not use the $default or
+any other consumer group that might already be in use. Reusing consumer groups
+among non-related consumers can cause expected behavior and possibly lost


typo: can cause unexpected behavior ?

acchen97

Looks good overall! Left some comments, though some of them are nits. Thanks for all your hard work on this @jakelandis @karenzone

acchen97 · 2018-07-20T01:44:36Z

docs/static/azure-module.asciidoc

+[[azure-dashboards]]
+==== Dashboards
+
+These {kib} dashboards are available and ready for you to use. You can use them they are, or tailor them to meet your needs.


You can use them as they are

acchen97 · 2018-07-20T01:45:50Z

docs/static/azure-module.asciidoc

+
+* *Overview*. Top-level view into your Azure operations, including info about users, resource groups, service health, access, activities, and alerts. 
+
+* *Alerts*. Alert info, including activity, alert status (activated, resolved, succeeded), and alerts heatmap


Sorry this is a nit but we can prob remove the "(activated, resolved, succeeded)" bit

acchen97 · 2018-07-20T01:47:43Z

docs/static/azure-module.asciidoc

+
+* *User Activity*. Info about system users, their activity, and requests.
+
+===== SQL database monitoring


For branding purposes, can we capitalize "Database"?

Same for the instances below as well

acchen97 · 2018-07-20T01:53:06Z

docs/static/azure-module.asciidoc

+
+* *SQL DB Database View*. Detailed info about each SQL database, including wait time, errors, DTU and storage utilization, size, and read and write input/output.
+
+* *SQL DB Queries*. Info about SQL database queries, including DTU Utilization, errors, and query duration and wait time. 


Let's exclude the last bit here. Just "info about SQL Database queries and performance" is fine.

acchen97 · 2018-07-20T01:57:57Z

docs/static/azure-module.asciidoc

+The Elastic Stack version 6.4 (or later) is required for this module. 
+
+NOTE: Logstash, Elasticsearch, and Kibana must run locally. You can also run 
+Elasticsearch, Kibana and Logstash on separate hosts to consume data from Azure.


I'm aware other modules like ArcSight have a similar statement here. To clarify the context, should be start this with "For these instructions below..."?

Seems like the Prereqs designation and the flow of the topic implies order. I avoid extra words whenever possible because "the more you write, the less people read."
If you feel strongly that there is risk of confusion, I will add.

acchen97 · 2018-07-20T02:00:08Z

docs/static/azure-module.asciidoc

+[[azure-module-prereqs]]
+==== Prerequisites
+
+The Elastic Stack and Microsoft Azure Event Hubs are required for this module.


Perhaps more accurately for the Azure side: "must have Azure Monitor enabled with Azure Event Hubs"

acchen97 · 2018-07-20T02:03:07Z

docs/static/azure-module.asciidoc

+Event Hubs. The `--setup` option creates an `azure-*` index pattern in
+Elasticsearch and imports Kibana dashboards and visualizations. 
+
+NOTE: The `--setup` option is intended only for first-time setup. If you include `setup` on subsequent runs, your existing Kibana dashboards will be overwritten.


Second "setup" here is missing the "--"

acchen97 · 2018-07-20T02:11:25Z

docs/static/azure-module.asciidoc

+Here are some guidelines to help you avoid data conflicts that can cause lost
+events.
+
+* **Create a {ls} consumer group.** 


@jakelandis are these best practices on the Azure website that we could link to or did you curate them yourself? My concern is that this content may go stale based on new Event Hub releases.

I curated them. I don't think the existing suggestions here will ever go out of fashion since it is at the core of how the event hubs work. However, there may be new (or existing) best practices not represented here.

The only best practice I found from MS is https://docs.microsoft.com/en-us/azure/event-hubs/event-hubs-faq#best-practices and most of their documentation is standard howto, configuration, pricing, etc. Not much consumer guidance.

Got it, thanks for the insight.

acchen97 · 2018-07-20T06:41:43Z

docs/static/azure-module.asciidoc

+
+NOTE: All Event Hubs options are common to both basic and advanced
+configurations, with the following exceptions. The basic configuration uses
+`event-hub-connections`. The the advanced configuration uses `event_hubs` and


@jakelandis this seems a bit confusing from a usability standpoint. The minor syntactical difference here may throw users off. Can you elaborate on why this is the case?

I'm happy to wait for more user feedback before we think too much into it though.

this seems a bit confusing from a usability standpoint

agreed. but needed.

The minor syntactical difference here may throw users off. Can you elaborate on why this is the case?

So... the configuration is either (pseudo configuration for illustration, not exact syntax):

event-hub-connections=[connection1, connection2, ...] threads=8

or

event-hubs |__ event-hub-connection=connection1, threads=8 |__ event-hub-connection=connection2, threads=4

the former supports many connections (hence the plural) the latter supports only 1 connection (hence the singular)

This is the same behavior as the input plugin for basic vs. advanced configuration. I think a user should see the discouragement of the advanced configuration (above) and not concern themselves with this ... or would copy/paste the example as a starting point (which has the correct syntax).

Got it, then in that case there may be a typo for the advanced config option as it says event_hubs with an underscore rather than a dash. /cc @karenzone

sorry, the underscores (and documentation) are correct. my above comment incorrectly used dashes instead of underscores.

actually... there is a typo above event-hub-connections should be event_hub_connections @karenzone sorry if misled you. All options should use underscores not dashes.

Corrected typo here and in azure_event_hubs plugin doc. Called attention to plural/singular treatment for emphasis. Let me know if this helps clarify.

acchen97 · 2018-07-20T06:44:21Z

docs/static/azure-module.asciidoc

+
+==== Azure module schema
+
+This module reads data from the Azure Event Hub and adds some additional structure to the data for Activity Logs and SQL Diagnostics. The original data is always preserved and any data added or parsed will be namespaced under 'azure'. For example, 'azure.subscription' may have been parsed from a longer more complex URN.


Love this section.

jakelandis · 2018-07-20T15:51:53Z

@karenzone - nice work! LGTM

dedemorton

Very minor comment about note formatting. Otherwise, LGTM. Nice work!

dedemorton · 2018-07-27T16:21:21Z

docs/static/azure-module.asciidoc

+* `look_back` reads `end` minus a number of seconds worth of pre-existing events.
+You control the number of seconds using the `initial_position_look_back` option.
+
+Note: If `storage_connection` is set, the `initial_position` value is used only


Need to write NOTE not Note if you want this to render in a note box.

Thanks for looking. In this case, I wanted to call out the info, but not with as much emphasis as the note box.

elasticsearch-bot · 2018-07-27T18:14:17Z

karen.metts merged this into the following branches!

Branch	Commits
master	`89ffcd1`
6.x	`288ef36`
6.4	`a919ef2`

Fixes #9510

karenzone added developer docs docs and removed developer docs labels May 2, 2018

karenzone force-pushed the azure branch from 98bb62e to 0a15740 Compare May 17, 2018 15:53

dedemorton mentioned this pull request May 23, 2018

Logstash 6.x doc changes #8683

Closed

49 tasks

acchen97 reviewed Jul 7, 2018

View reviewed changes

jakelandis reviewed Jul 9, 2018

View reviewed changes

dedemorton suggested changes Jul 17, 2018

View reviewed changes

jakelandis reviewed Jul 18, 2018

View reviewed changes

karenzone force-pushed the azure branch from 6b51f01 to 83488ff Compare July 18, 2018 14:25

jakelandis reviewed Jul 19, 2018

View reviewed changes

acchen97 reviewed Jul 20, 2018

View reviewed changes

dedemorton approved these changes Jul 27, 2018

View reviewed changes

Add azure module doc

85d0329

karenzone force-pushed the azure branch from 3ba987d to 85d0329 Compare July 27, 2018 18:11

elasticsearch-bot pushed a commit that referenced this pull request Jul 27, 2018

Add azure module doc

a919ef2

Fixes #9510

elasticsearch-bot closed this in 89ffcd1 Jul 27, 2018

elasticsearch-bot pushed a commit that referenced this pull request Jul 27, 2018

Add azure module doc

288ef36

Fixes #9510

karenzone deleted the azure branch July 27, 2018 18:23

karenzone mentioned this pull request Aug 16, 2018

Add documentation for Azure Module #9499

Closed


		These {kib} dashboards are available and ready for you to use.

		* Overview. Top-level view into your Azure operations, including info about users, resource groups, service health, access, activities, and alerts.


		Microsoft is the best source for the most up-to-date Azure information.

		* [Overview of Azure Monitor]https://docs.microsoft.com/en-us/azure/monitoring-and-diagnostics/monitoring-overview-azure-monitor



		[id="plugins-{type}s-{plugin}-event_hub_connection"]
		===== `event_hub_connection`

		* [Azure SQL Database metrics and diagnostics logging]https://docs.microsoft.com/en-us/azure/sql-database/sql-database-metrics-diag-logging
		* [Stream the Azure Activity Log to Event Hubs]https://docs.microsoft.com/en-us/azure/monitoring-and-diagnostics/monitoring-stream-activity-logs-event-hubs


		* Overview. Top-level view into your Azure operations, including info about users, resource groups, service health, access, activities, and alerts.

		* Alerts. Alert info, including activity, alert status (activated, resolved, succeeded), and alerts heatmap


		* User Activity. Info about system users, their activity, and requests.

		===== SQL database monitoring


		* SQL DB Database View. Detailed info about each SQL database, including wait time, errors, DTU and storage utilization, size, and read and write input/output.

		* SQL DB Queries. Info about SQL database queries, including DTU Utilization, errors, and query duration and wait time.


		==== Azure module schema

		This module reads data from the Azure Event Hub and adds some additional structure to the data for Activity Logs and SQL Diagnostics. The original data is always preserved and any data added or parsed will be namespaced under 'azure'. For example, 'azure.subscription' may have been parsed from a longer more complex URN.

Add azure module doc #9510

Add azure module doc #9510

Conversation

karenzone commented May 2, 2018 • edited Loading

karenzone commented May 17, 2018

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

acchen97 commented Jul 7, 2018

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

karenzone Jul 13, 2018 • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

karenzone commented Jul 17, 2018

dedemorton left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

jakelandis Jul 18, 2018 • edited Loading

Choose a reason for hiding this comment

jakelandis Jul 18, 2018 • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

jakelandis commented Jul 18, 2018

karenzone commented Jul 18, 2018

Choose a reason for hiding this comment

acchen97 left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

karenzone Jul 23, 2018 • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

jakelandis commented Jul 20, 2018

dedemorton left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

elasticsearch-bot commented Jul 27, 2018

karenzone commented May 2, 2018 •

edited

Loading

karenzone Jul 13, 2018 •

edited

Loading

jakelandis Jul 18, 2018 •

edited

Loading

jakelandis Jul 18, 2018 •

edited

Loading

karenzone Jul 23, 2018 •

edited

Loading