Add better logging for backend components

[S-ayanide]

Description

Currently, our server logs provide limited information, making it difficult to diagnose issues and track user activity. To address this, I propose that we enhance our server logs with additional fields that provide more context and insights.

Here are some suggested fields that we can add to our server logs:

• Request metadata: Adding request metadata fields like request ID, request URL, and request method can help us identify and trace specific requests, making it easier to diagnose issues and track user activity.
• User metadata: Adding user metadata fields like user ID, user IP address, and user agent can help us identify and track user activity, making it easier to monitor and analyze user behavior.
• Server metadata: Adding server metadata fields like server hostname, server IP address, and server time can help us identify and diagnose issues related to server performance and availability.
• Custom fields: Adding custom fields like application-specific metadata can help us track and analyze application-specific events and behaviors.

Implementation specifications

        logFields := logrus.Fields{
		"projectId": identifiers.ProjectIdentifier,
		"user": identifiers.User,
		"component": "GraphQL server"
	}

	logrus.WithFields(logFields).Info("request received to create a new delegate")

By adding these fields, we can significantly improve the quality and usefulness of our server logs, making it easier to diagnose issues, track user activity, and monitor server performance.

[S-ayanide]

@namkyu1999 assigning this task to you, based on the server logging discussion as a part of LFX.

[namkyu1999]

Good! I can handle it!

[JAYESHBATRA]

Is this issue still available ? If yes then please assign it to me.

[imrajdas]

Hi @JAYESHBATRA , these issues are part of LFX and our current mentee(@namkyu1999 ) is working on this. Please feel free to take any other open issue. Or apply for the next LFX term.

[imrajdas]

Hey @JAYESHBATRA, Please take up these issues if you're interested.

1. Move the CUSTOM_TLS_CERT from subscriber config to subscriber secret #3943
2. Use kubernetes patch instead of get-update in subscriber for updating cm and secret #3944

[JAYESHBATRA]

Hi @imrajdas ,

Sure, I'd be happy to take up the issues you've raised.

[S-ayanide]

The updated logging setup has been merged, as an improvement we added parameters like method, URI, status, latency and clientIP with requests to structure as well as identify the logs better.

PR for reference: #3939

Closing this issue since the task has been resolved.