You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The API manager is configured to use ELK analytics. When a request fails due to a reason such as authentication failure, we do not log the user IP (X-forwarded header). But in success scenarios, this header is printed.
Include the user IP in failure scenarios as well.
Steps to Reproduce
Enable ELK analytics in deployment.toml
Enable additional logs as per the documentation.
Check the apim_metrics.log for a success and failed scenario
Affected Component
Analytics
Version
4.1
Environment Details (with versions)
No response
Relevant Log Output
No response
Related Issues
No response
Suggested Labels
No response
The text was updated successfully, but these errors were encountered:
Description
The API manager is configured to use ELK analytics. When a request fails due to a reason such as authentication failure, we do not log the user IP (X-forwarded header). But in success scenarios, this header is printed.
Include the user IP in failure scenarios as well.
Steps to Reproduce
Enable ELK analytics in deployment.toml
Enable additional logs as per the documentation.
Check the apim_metrics.log for a success and failed scenario
Affected Component
Analytics
Version
4.1
Environment Details (with versions)
No response
Relevant Log Output
No response
Related Issues
No response
Suggested Labels
No response
The text was updated successfully, but these errors were encountered: