Universal splunk forwarder as sidecar not showing internal splunk logs

[hemanth4]

I have implemented a sidecar container to forward my main application logs to splunk. Have used universalsplunkforwarder image. After I deploy both my main application and forwarder seems up and running. But anyway not recieving any logs in splunk index specified. To troubleshoot splunkd log or any specific splunk internal logs are not found in /var/log path. Can someone please help how we enable this splunk internal logs?

[xshkurti]

@hemanth4 
Thank you for your post here. This seems most likely like a Splunk configuration issue so I think it is better to ask on that forum.

After doing a little research I found this link that might point you in the right direction in case FortiGate or FortiAnalyzer is involved:

How to configure Splunk forwarder to receive Forti... - Splunk Community

If no FortiGate or other Fortinet products are involved, then you should check with the other vendors on how to get and view logs in Splunk.

[saichinnu1852]

To connect your AWS API through MuleSoft, ensure that your MuleSoft HTTP Request component is correctly configured. You should set the AWS API endpoint in the HTTP Request connector, configure the method (GET, POST, etc.), and pass the necessary headers, such as authentication tokens (e.g., AWS Signature or Bearer Token). Ensure that the connection timeout and response timeout are set appropriately. If your API requires SSL, make sure the MuleSoft HTTP Request supports HTTPS with the correct SSL configuration. You may also need to whitelist your MuleSoft IP in the AWS API Gateway for security. Test with logging to capture detailed error information for troubleshooting.