DevOps Fest 2019. Игорь Фесенко. DevOps: Be good, Get good or Give up
- 2. ifesenko.com
- 10. I went to an all night JavaScript hackathon and by morning we finally had the build process configured!
- 11. Clean Build Unit Tests (NUnit, xUnit, MSTest) Test Coverage Static Analysis SonarQube Versioning StyleCop Package Publish Package Restore
- 24. Why do I need that? Why was my VM’s CPU% so high? Do we need to throw in more VMs process this load? Can you download and send me the logs next time this happens? Who shut down this database and when?
- 27. Record Transmit Analyze Store Delete
- 28. Record Transmit Store Delete
- 29. Record Delete
- 30. “Show me all the error log messages where the order values is more than $20,000 or the customer is a VIP”
- 31. “Show me all the failed login attempts for user Igor where the server name was LoginServer4”
- 32. “Show me all the login attempts for loginServer4 where the database read time was more than 250ms”
- 33. “How many users used the export to CSV feature of ApplicationX where the total order value was less than $100,000”
- 34. Semantic Logging is creation of logs with machine’s consumption in mind
- 35. • Be careful • CDNs fail, but you scripts don’t have to (or you use eCDN) • Do NOT include files directly from GitHub in PRODUCTION (via https://rawgit.com/) • Use Subresource Integrity
- 36. • Be careful • Do NOT cache any of resources/responses for Auth/Authz flow • Do NOT remove old version of assets when you are deploying new ones
- 41. • Peak CPU utilization • Allocated and peak RAM usage • Storage capacity • Occupancy • Input/output Operations Per Second (IOPS) • and more…
- 42. Azure Advisor
- 44. what size of VM would you create?
- 45. your bill will be paid by someone else
- 46. Does your answer change?
- 51. Questions @ky7m | ifesenko.com | ifesen@softserveinc.com
Editor's Notes
- #41: Receive a performance analysis on compute, storage, and network resources based on observed peak CPU utilization, allocated and peak RAM usage, storage capacity, occupancy, Input/output Operations Per Second (IOPS), and more.
- #50: Identify the best cloud configuration for optimal performance at the lowest possible cost based on comprehensive system-level data analysis (such as peak CPU, memory, IOPS, and network usage).