Contact person: Fix Error Logs & Deploy

Phone:Show

Email:Show

Location: Oviedo, United States

Budget: Recommended by industry experts

Time to start: As soon as possible

Project description:
"I’m seeing a millions of error logs flooding in the server and need a sharp set of eyes to pinpoint what’s going wrong. The entries point to both the application layer and our SQL-based back-end. Iexpect investigation at code level as well as in the database objects—queries, indexes, stored procedures, anything that could be triggering the noise.

Here’s how I’d like the engagement to flow:

• Diagnosis and root-cause report that clearly states why the errors are produced, referencing specific code blocks or DB calls.
• Clean, tested fixes applied in UAT: code patches committed, database scripts executed, and evidence that the error log remains clean under load.
• Promotion of the verified changes to production through our normal release pipeline (Git, CI/CD, and standard rollback plan).

Acceptance is straightforward: no recurring error logs for 48 hours after deployment, automated tests pass, and the production push goes through without regression.

If you’re comfortable diving into log files, refactoring application code, and tweaking SQL performance all in one sprint, let’s get started." (client-provided description)