Improve error traceability by modifying generic API error strings

[gaurav6386]

What did you do?

Entered incorrect SMTP credentials for the Alertmanager service or simulated other errors (e.g., invalid template string) through the APIs in the Alertmanager.

What did you expect to see?

Expected to see custom error message, provided for each functions where error originated.

What did you see instead? Under which circumstances?

We are receiving a generic 'API Error' message in the server logs instead of the custom messages provided to the API error handler. This prevents accurate diagnosis of API issues. The custom message passed as the third argument to the respondError function is not being utilized in the server logs for both the Alertmanager service and the Signoz's query-service.

Environment

• Operating System: Ubuntu 22.04.1 LTS

• System Information: Linux 6.5.0-1022-aws x86_64

• Alertmanager Version: 0.23.0 (branch: HEAD, revision: eaf816bfe5ad0c7cebdb9aeb4113d2ee7428udb)

  • Build User: root@u3hedn84923
  • Build Date: 20240123-10:03:32
  • Go Version: go1.17.13
  • Platform: linux/amd64

• Alertmanager Configuration File: NA

• Prometheus Configuration File: NA

• Logs:
  AlertManager:
  
  Signoz: