Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
In Splunk the 'cluster_name' variable is not populating with actual name of cluster but instead with default value of cluster_name
See original GitHub issueWhat happened: The cluster_name variable value is not populating with the actual name of the cluster instead default value of cluster_name is in the field when querying in Splunk.
What you expected to happen: The actual name of the cluster to be showing under cluster_name variable in Splunk.
How to reproduce it (as minimally and precisely as possible): Deployed Splunk connect using Helm charts via https://github.com/splunk/splunk-connect-for-kubernetes/tree/develop/helm-chart/splunk-connect-for-kubernetes.
Anything else we need to know?: Using latest Splunk connect for kubernetes 1.4.1 release.
Environment:
- Kubernetes version (use
kubectl version): GitVersion:“v1.15.7-gke.32” - Ruby version (use
ruby --version): Not installed - OS (e.g:
cat /etc/os-release): Ubuntu 18.04.4 LTS - Splunk version: 7.3.0
- Others:
Issue Analytics
- State:
- Created 3 years ago
- Reactions:1
- Comments:8 (3 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Hey @r6ricer did you try setting the value https://github.com/splunk/splunk-connect-for-kubernetes/blob/develop/helm-chart/splunk-connect-for-kubernetes/values.yaml#L41 ?
Thanks @r6ricer . Make sense to me. Created a Jira ticket https://jira.splunk.com/browse/ADDON-27949. Will plan it in future.