- Member of Marketplace team - Manager IaC with Terraform - Daily automation with Python, Bash and Rundeck - Observability with Grafana, Prometheus and another current DevOps tools - Helping internal projects

- Deployment of metrics and logs systems in a centralized way
- CI/CD deployment to automatically deploy applications
- Migrating applications to run on Docker/Kubernetes
- Using AWS and trying to standardize the environment
- Documentation

Site Reliability Engineer

Member of the SRE Tools group, which uses tools to collect logs, metrics, tracing and alerts. We try to insert automation in everything, be it Python script, Golang, Ansible or just shell script.

One of the cool projects that I was responsible for the evolution, was the tool that gives visibility to the infrastructure environment, such as information from the instances, the BIG-IP and etc. The stack for this application was finished with Flask + SemanticUI on the frontend, FastAPI + Elasticsearch on the backend and Golang on the CLI.

The idea at the moment is to make the tools more stable and more automated. Of course, passing on the knowledge to the other squads, so they both win. On our side the optimization of resources and on the other a better user experience.

02/21/2020 - PRAD Award (High Performance Recognition Program)

It was here that I learned about the docker, the frustrations and the facilities that this platform proposes. At the time, they were building a Devops team, as I always liked automation and I had enough knowledge to know how things worked in the system, from the request in GTM to the application X answer, why not face this new journey? It was here that they gave me the opportunity to work as a middleware between the Ops and the Devs.

I was able to implement some systems, from architecture to deployment with automation. Like the ELK stack, in the best possible practices and everything via ansible playbook. With that I made the change of collection of logs of Swarm with Fluentd; I was able to implement Traefik too, to make life easier for the developer, leaving him with more autonomy in the routes of his applications without having to go through an administrator or something in the bureaucratic sense; A very cool feat, too, was the implementation of Grafana with auto-commit in which the dashboards were read-only and could only be changed in the repository, thus performing the automatic deployment; Here I did justice to the use of Ansible too, cloned recipes migrating to the playbook and created from scratch as well, such as the implementation/alteration of the ELK stack. Anyway, some things that I managed to implement that I believe to be used until today.

Thanks Catho for this opportunity, the learning was really good.

Senior Linux Administrator

Despite the experience obtained in previous jobs, I always tested things before at home - of course, what was possible - so at Centrix I already joined the company knowing how to assemble/disassemble a computer and knew the names of the boards and what they did. It was no different here, I already knew Linux, at least the basics yes. So with this curiosity and trying to understand how things worked, they gave me the opportunity to join the team of Linux administrators, effectively messing with CentOS 6/7, Chef, Rundeck, Jenkins, Git, among others.

My Python learning started from here, with real problems. I always tried to do tasks with this language, even if it was simple and easy - like a one-line shell script - of course, by learning. As much as everything was already created and in the beginning I just wanted to keep things working, I had the opportunity to implement solutions that never existed, such as local tests and standardization of Chef's recipes, plugins/checks for OMD, business sensors that performed the scraping of x time and sent it to Elasticsearch.

As much as most things were already implemented and functional, it was very easy to test solutions, as there was no bureaucracy. And as much as X solution was already there, there was always something that could be adjusted... It is like the code of an application, if you look at the same code again after some days, there will be something to be improved or functions to be implemented. And so is the life of the system administrator, we always have to be attentive to new versions of applications, such as updating the firewall, good practices such as not using robocop but foodcritic in Chef's recipes, how to be more productive using X method and spreading it to the team for testing, etc.

Not to mention the maintenances made at night with pizza and coke. Anyway, great experience.

Personal details

Wellington O.

Summary

Technical skills

Work Experience

Certifications & Awards