- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Splunk Add-on for DynaTrace
Hi there,
I have configured Dynatrace add-on with proxy setup enabled (coz of firewall issue), if I run the dynatrace url using the api token through postman I am getting data for all the endpoints.
But in splunk we are getting connectionpool.py and modinput.py error for the Dynatrace API Version 2 input.
DEBUG pid=xxxxx tid=MainThread file=connectionpool.py:_new_conn:1018
DEBUG pid=xxxxx tid=MainThread file=base_modinput.py:log_debug:298
please guide me to fix this issue, thank you
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hey there,
I understand you're facing errors with the Dynatrace API Version 2 input in Splunk, even though the API works fine in Postman. Don't worry, I've got some troubleshooting steps to help you out:
1. Proxy Check:
- Double-check your proxy settings in Splunk's proxy.conf. Are they accurate and match your environment?
- Can you connect to the Dynatrace API endpoint through the proxy using tools like curl or wget from the Splunk server?
2. Log Detective:
- Look for clues in Splunk's splund.log and python.log. Are there any error messages related to proxy, connection, or certificates?
- Enable debug logging for the Dynatrace add-on to get more details about connection attempts.
3. Certificate Confusion (if applicable):
- If using SSL/TLS, are the certificates trusted and installed correctly?
- As a temporary test, try disabling certificate verification in Splunk (not recommended for production!).
4. Network Ninja:
- Check firewalls on both Splunk and the proxy server for blocked connections to the Dynatrace API.
- Can you connect directly to the API endpoint from the Splunk server, bypassing the proxy?
5. Token Tweak:
- Try regenerating your Dynatrace API token and updating it in Splunk. Does it have the necessary permissions?
6. Version Vault:
- Consider upgrading or downgrading the Dynatrace add-on or Splunk itself for better compatibility.
- Make sure the add-on version works with your Splunk version.
Stuck?
Don't hesitate to reach out to Splunk or Dynatrace support for further assistance. Provide them with details about your environment, configuration, and error messages.
Remember, I'm here to help you troubleshoot like a pro!
~ If the reply helps, a Karma upvote would be appreciated
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I have a similar/same problem, the logs explicitly state that the certficate validation failed due to a self-signed cert in the chain.
Your ideas was:
"As a temporary test, try disabling certificate verification in Splunk (not recommended for production!)."
How would I do this for the dynatrace plugin?
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thank you for your reply, I will do the debugging based on your input and will keep you posted.
