Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

How to Use the TICK Stack, CoreOS, & Docker to Make Your SaaS Offering Better

253 views

Published on

Other than InfluxDB and the open source Tick Stack, InfluxData provides a SaaS version of the TICK Stack, called InfluxCloud, that supports clustering, authentication and other enterprise features not found in the open source TICK Stack. InfluxCloud is designed to be easy to use and reliable for our customers, as they rely on this service to store time series data gathered from sensors, servers, and other devices that is the foundation for their own SLAs for their products and services. This means InfluxCloud requires an even higher standard of service in order to help them maintain their service level commitments.

Published in: Software
  • Be the first to comment

  • Be the first to like this

How to Use the TICK Stack, CoreOS, & Docker to Make Your SaaS Offering Better

  1. 1. © 2017 InfluxData. All rights reserved.1 11th July 2017 How to use the TICK Stack, CoreOS, & Docker to make your SaaS offering better
  2. 2. © 2017 InfluxData. All rights reserved.2 Agenda ¨ What is InfluxCloud ¨ Monitoring InfluxCloud ¨ Q&A
  3. 3. © 2017 InfluxData. All rights reserved.3 Introduction Gianluca Arbezzano, SRE Docker Captain, open source maniac and grower of fruit and vegetables. Email: gianluca@influxdb.com Twitter: @GianArb community.influxdata.com About me
  4. 4. © 2017 InfluxData. All rights reserved.4 © 2017 InfluxData. All rights reserved.4 Founded in 2013 Delivering a modern open source platform for metrics and events Guiding principles: Developer Happiness Ease of Development + Scale Out Time to Value Results 70,000+ Active Servers 10,792 GitHub stars 300+ Customers (Cloud and Enterprise Offering) InfluxData Overview
  5. 5. © 2017 InfluxData. All rights reserved.5 What is InfluxCloud? ¨ Time Series Database as a Service ¨ A great use case to build better production ready tools ¨ A way to make money ¨ Monitoring is perfect as a third party service ¨ It needs to be up when your system is down ¨ If you are not making monitoring, it’s not your core business. Maintain it can be expensive
  6. 6. © 2017 InfluxData. All rights reserved.6 InfluxCloud Architecture - high level
  7. 7. © 2017 InfluxData. All rights reserved.7 Design consideration ¨ Speed to deploy a cluster needs to be reasonable. ¨ Machines needs to be able to communicate cluster membership. ¨ Cluster services can be restarted easily. ¨ Support team need to be confident about the system.
  8. 8. © 2017 InfluxData. All rights reserved.8 InfluxCloud Architecture - Cloud
  9. 9. © 2017 InfluxData. All rights reserved.9 InfluxCloud Architecture - focus on single cluster
  10. 10. © 2017 InfluxData. All rights reserved.10 InfluxCloud Architecture - focus on single instance
  11. 11. © 2017 InfluxData. All rights reserved.11 InfluxCloud Architecture - why CoreOS? ⠒ Designed to deploy containers ⠒ Auto update ⠒ To get all the flexibility we need to tread every cluster as special
  12. 12. © 2017 InfluxData. All rights reserved.12 Monitoring Data flow ⠒ Docker send all container logs to a central place ⠒ Every server has a Telegraf agent to get system information (CPU, memory, ios) ⠒ For service metrics, Influxdb, Kapacitor, etc. everything sends metrics to InfluxCloud for monitoring
  13. 13. © 2017 InfluxData. All rights reserved.13 Monitoring Data flow - Dashboard
  14. 14. © 2017 InfluxData. All rights reserved.14 Kapacitor for alerting
  15. 15. © 2017 InfluxData. All rights reserved.15 Kapacitor to build stats
  16. 16. © 2017 InfluxData. All rights reserved.16 Continuous delivery every time it’s possible
  17. 17. © 2017 InfluxData. All rights reserved.17 Don’t trust anyone! Monitor your monitor
  18. 18. © 2017 InfluxData. All rights reserved.18 What we learned ⠒ Build tools and utilities that restrict access to the AWS console (improve security, gain control, less human error) ⠒ Monitor to identify repetitive support tasks ⠒ People needs visibility on their cloud services ⠒ Metrics are everywhere. The number of alerts is a good metric. Now we build alerts on alerts ⠒ Proactive monitoring and proactive-automation
  19. 19. © 2017 InfluxData. All rights reserved.19 What now? InfluxCloud next-gen ⠒ Co-monitoring between InfluxData and customers ⠒ Chronograf and Kapacitor as basic add-ons in every new clusters ○ Welcome the Tick stack in the cloud! ⠒ The support team grows with the platform ○ Better tools, better UI, better everything! ⠒ Glue the API offered by all tools and productions that we are building/using to build the perfect experience
  20. 20. © 2017 InfluxData. All rights reserved.20 We are building trust. Co-monitoring
  21. 21. © 2017 InfluxData. All rights reserved.21 Conclusion
  22. 22. © 2017 InfluxData. All rights reserved.22 Next Steps Visit InfluxData.com Download the TICK Stack or try InfluxEnterprise Ask Questions on the community: community.influxdata.com

×