Monitor logs, metrics, pings, and traces of your distributed (micro-) services. There are also slides walking you through the features of this repository.

1. Metricbeat System: Show the [Metricbeat System] Overview dashboard in Kibana and then switch to [Metricbeat System] Host overview with auto-refresh, run bad.jar with java -Xmx512m -jar /opt/bad.jar, and see the spike. Optionally build a nicer overview with the Time Series Visual Builder.
2. Packetbeat: Show the [Packetbeat] Overview, [Packetbeat] Flows, and [Packetbeat] HTTP dashboard, let attendees hit /, /good, /bad, and /foobar a few times, and see the corresponding graphs. Optionally show the [Packetbeat] DNS Tunneling and [Packetbeat] TLS Sessions dashboards as well.
3. Filebeat modules: Show the [Filebeat Nginx] Access and error logs, [Filebeat System] Syslog dashboard, and [Filebeat System] SSH login attempts dashboards.
4. Filebeat: Let attendees hit /good with a parameter and point out the MDC logging under json.name and the context view for one log message. Let attendees hit /bad and /null to show the stacktrace both in the JSON log file and in Kibana by filtering down on application:java and json.severity: ERROR. Also point out the meta.* information and json.stack_hash, which you could also visualize in a bar chart.
5. Auditbeat: Show changes to the /opt/ folder with the [Auditbeat File Integrity] Overview dashboard.
6. Heartbeat: Run Heartbeat and show the Heartbeat HTTP monitoring dashboard in Kibana, then kill the frontend application and see the change.
7. Metricbeat nginx: Show the values of nginx.stubstatus and optionally visualize nginx.stubstatus.active.
8. Metricbeat HTTP: Show /health and /metrics with cURL (credentials are admin and secret). Then collect the same information with Metricbeat's HTTP module and show it in Kibana's Discover tab.
9. Metricbeat JMX: Display the same /health and /metrics data and its collection through JMX.
10. Visual Builder: Build a more advanced visualization with the Time Series Visual Builder, for example the heap usage and include the deployment events as an annotation.
11. Sleuth & Zipkin: Show the traces in the log so far. Then let the attendees hit /call and /call-bad to see where the slowness is coming from and how errors look like. Also use the Zipkin Chrome extension to show the current call. And you can even use the ZIPKIN_UI_LOGS_URL to link back to the relevant Kibana logs.
12. Kibana Dashboard Mode: Point attendees to the Kibana instance to let them play around on their own.

If the network connection is decent, show it on Amazon Lightsail. Otherwise fall back to the local setup and have all the dependencies downloaded in advance.

Make sure you have run this before the demo, because some steps take time and require a decent internet connection.

1. Make sure you have your AWS account set up, access key created, and added as environment variables in AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY. Protip: Use https://github.com/sorah/envchain to keep your environment variables safe.
2. Create the Elastic Cloud instance with the same version as specified in variables.yml's elastic_version, enable Kibana as well as the GeoIP & user agent plugins, and set the environment variables with the values for ELASTICSEARCH_HOST, ELASTICSEARCH_USER, ELASTICSEARCH_PASSWORD, as well as KIBANA_HOST, KIBANA_ID.
3. Change into the lightsail/ directory.
4. Change the settings to a domain you have registered under Route53 in inventory, variables.tf, and variables.yml. Set the Hosted Zone for that domain and export the Zone ID under the environment variable TF_VAR_zone_id. If you haven't created the Hosted Zone yet, you should set it up in the AWS Console first and then set the environment variable.
5. If you haven't installed the AWS plugin for Terraform, get it with terraform init first. Then create the keypair, DNS settings, and instances with terraform apply.
6. Open HTTPS on the network configuration on all instances (waiting for this Terraform issue).
7. Apply the base configuration to all instances with ansible-playbook --inventory-file=inventory configure_all.yml.
8. Apply the instance specific configuration with ansible-playbook --inventory-file=inventory configure_monitor.yml — frontend and backend don't have specific configurations.
9. Deploy the JARs with ansible-playbook --inventory-file=inventory deploy_bad.yml, ansible-playbook --inventory-file=inventory deploy_backend.yml, ansible-playbook --inventory-file=inventory deploy_frontend.yml, and ansible-playbook --inventory-file=inventory deploy_zipkin.yml (Ansible is also building them).

When you are done, remove the instances, DNS settings, and key with terraform destroy.

Make sure you have run this before the demo, because some steps take time and require a decent internet connection.

1. Change into the local/ directory.
2. Run docker-compose up, which will bring up Elasticsearch, Kibana, and all the Beats.
5. Run the Java applications from their directories with gradle bootRun.

When you are done, stop the Java applications and remove the Docker setup with docker-compose down -v.

• MySQL on the backend with TCP Heartbeat monitoring
• Docker
• Fix Metricbeat for HTTP /metrics
• Improve traced methods and add async
• https://www.elastic.co/guide/en/logstash/current/plugins-outputs-cloudwatch.html (https://aws.amazon.com/about-aws/whats-new/2017/09/amazon-route-53-announces-support-for-dns-query-logging/ etc)?
• http://docs.spring.io/spring-boot/docs/current/reference/html/production-ready-metrics.html?