Linux & Docker audit
Inventory, exposure, logs, resources, backups, and a prioritized correction plan.
Open to scoped technical work · Argentina
I'm Lautaro, a SysAdmin and Backend Developer. I help small teams stabilize Linux/Docker systems, verify backups, improve observability, and automate processes without starting with an impossible-to-scope project.
Every engagement starts with a stage that can be understood, priced, and verified before the scope grows.
Inventory, exposure, logs, resources, backups, and a prioritized correction plan.
Scoped changes, encrypted backups, recovery testing, and rollback documentation.
Useful alerts, operational dashboards, and troubleshooting for services that need to stay up.
A measurable first automation across APIs, Sheets, Notion, Telegram, or existing systems.
A solution is only good if it remains easy to operate after the handoff.
What is happening today, what cannot break, and how the result will be validated.
A small first stage with deliverables, boundaries, and acceptance criteria.
Observable changes, reversible where appropriate, backed by evidence.
Documentation, open items, and a clear way to operate afterwards.
Production reliability improved
A fleet of production Linux servers was running a monitoring agent version approaching end of support. The migration covered messaging, DRM, licensing and backend services.
impact
Approximately 50 hosts were migrated by Lautaro. No rollback was required, and no host lost monitoring visibility for more than approximately two minutes.
Operational cost improved
A UAT environment needed to run a representative stress test before a high-traffic event, but its standard capacity was not enough to model the expected load.
impact
The stress test passed without issues. The temporary capacity increase provided a representative test profile without leaving permanent overprovisioning afterward.
Incident stabilized
Consumers connected to a production RabbitMQ cluster were not processing messages fast enough. The backlog grew and the affected node became stuck under resource pressure.
impact
The manual flush discarded queued messages but prevented the stuck node from continuing toward a more severe resource-exhaustion condition. The exact recovery time is not documented.
Have a concrete problem?
Tell me what is failing, what you want to improve, and what cannot break. I will reply with an initial read and a proposed first stage.