| global | |
| log stdout format raw local0 | |
| defaults | |
| log global | |
| mode http | |
| timeout connect 4s | |
| timeout client 30s | |
| timeout server 10s | |
| option redispatch | |
| option forwardfor |
| #!/usr/bin/ruby | |
| # run like ./http-server.rb 8000 | |
| require 'webrick' | |
| server = WEBrick::HTTPServer.new(:Port => ARGV.first) | |
| server.mount_proc '/' do |req, res| | |
| puts req.header | |
| puts req.body |
| -- This is useful to see counters that are updated while executing the query. This provides useful information | |
| -- about number of times the DB executed operations over indices or tables. It also provides information about | |
| -- the sorting process. More info about counters: https://fromdual.com/mysql-handler-read-status-variables | |
| -- ****** When you have enough permissions to flush server status counters ****** | |
| FLUSH STATUS; | |
| -- QUERY TO ANALYZE |
| SHOW ENGINE INNODB STATUS; | |
| -- Transactions waiting for a lock, including blocking transaction details | |
| SELECT | |
| waiting_trx.trx_id AS waiting_trx_id, | |
| waiting_trx.trx_started AS waiting_trx_started, | |
| waiting_trx.trx_state AS waiting_trx_state, | |
| waiting_trx.trx_rows_locked AS waiting_trx_rows_locked, | |
| waiting_trx.trx_rows_modified AS waiting_trx_rows_modified, | |
| waiting_trx.trx_mysql_thread_id AS waiting_thread, |
| -- List running queries | |
| SELECT * FROM INFORMATION_SCHEMA.PROCESSLIST WHERE command = "Query" ORDER BY TIME DESC; | |
| -- Indexes size | |
| SELECT database_name, table_name, index_name, stat_value AS pages, | |
| round(stat_value*@@innodb_page_size/1024/1024, 2) size_in_mb | |
| FROM mysql.innodb_index_stats | |
| WHERE stat_name = 'size' | |
| ORDER BY 4 DESC; |
En esta charla cuento sobre un proceso que diseñamos, inspirados en la medicina, para clasificar y priorizar todos los errores que aparecen en nuestro sistema de forma inesperada. De forma de poder conocer el 100% de los errores que ocurren y poder tener feedback continuo sobre el estado del sistema, algo que es muy importante cuando se utiliza continuous deployment.
Slides: https://www.slideshare.net/Azagthot/clasificacion-y-priorizacion-distribuida-de-errores-y-bugs
En esta charla cuento mi experiencia trabajando en un proyecto para una empresa de Estados Unidos en donde pasamos de un modelo de release train con releases diarios a continuous deployment con múltiples releases por día. Todo esto lo logramos sin tener ningun equipo de QA ni de operaciones, solo developers.
Slides: https://www.slideshare.net/Azagthot/continuous-deployment-sin-equipos-de-qa-ni-de-ops-80834132
| def remote_csv(url) | |
| CSV.new(open(url)) | |
| end |
| class SchemaMigration < ActiveRecord::Base; self.primary_key = :version; end |
| force_skip = ['master', 'develop'].include? `git rev-parse --abbrev-ref HEAD`.strip | |
| diff_files = [] | |
| # Note: ACMRTUXB is all file types except delete | |
| diff_files.concat(`git --no-pager diff --name-only --diff-filter='ACMRTUXB' origin/develop...`.split(/\n/)) | |
| diff_files.concat(`git --no-pager diff --name-only --diff-filter='ACMRTUXB' --cached`.split(/\n/)) | |
| if force_skip || diff_files.empty? | |
| # so that rubocop doesnt run any tests | |
| puts '-v' |