Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] leave the httpevent outputServers as it is #356

Closed
YifengMao opened this issue Dec 19, 2019 · 1 comment
Closed

[BUG] leave the httpevent outputServers as it is #356

YifengMao opened this issue Dec 19, 2019 · 1 comment
Assignees
Labels
bug Malfunctioning Eventgen due to potential bug

Comments

@YifengMao
Copy link
Contributor

Describe the bug
hostname will be automatically converted to ip addr in setup() api:
` self.discovered_servers = []
for host in hosts:
try:
formatted_hostname = socket.gethostbyname(host)
if new_key:
key = create_new_hec_key(formatted_hostname)
except (socket.gaierror, requests.ConnectionError):
self.logger.warning('failed to reach %s, skip...' % host)
continue
except (ValueError, KeyError):
self.logger.warning('failed to setup hec token for %s, skip...' % host)
continue

            self.discovered_servers.append({"protocol": str(protocol), "address": str(formatted_hostname), "port": str(hec_port), "key": str(key)})

`
if i have a dynamic provisioned splunk behind a fixed FQDN, i don't have any workarounds to make it work. Is it possible to leave the host as it is in setup stage?

@YifengMao YifengMao added the bug Malfunctioning Eventgen due to potential bug label Dec 19, 2019
@jcmia1
Copy link

jcmia1 commented Dec 20, 2019

I am seeing issues reported in this forum discussions: https://forums.aws.amazon.com/message.jspa?messageID=714343. This means in-flight events could be sending to a wrong destination IF the IPs change. I have already experienced this in our labs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Malfunctioning Eventgen due to potential bug
Projects
None yet
Development

No branches or pull requests

7 participants