-
Notifications
You must be signed in to change notification settings - Fork 24
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
Queue processor could not get initial token and will terminate. #34
Comments
Anyone? |
Hi @GamerGun! Unfortunately, we don't not provide any support for custom implementations but it may because of your outbound rules. It seems you can not reach out that endpoint. |
Could you please be sure you provide correct apiKey and baseUrl? Also you should guarantee that your client is able to reach the endpoint as @cemkucuk said. The endpoint returns the security token which is an internal logic and if the apiKey is correctly provided, no need to worry about the token. |
Thank you guys. |
@GamerGun, it should work with given api key after creation of OEC Action Channel. Please use that one because irrelevant api keys of your account can not work with OEC client. |
Hi @GamerGun, I hope you solved API Key issue. API Keys that belong to Opsgenie Actions or Integrations would work with OEC. Also, please be sure your configuration file is updated correctly. You can find open bugs and suggestions for OEC on our public issue tracker. If you are experiencing an issue with OEC, or if you want to raise a new bug or suggestion you can reach out Opsgenie support. |
Hi,
We are in the process of running OEC on a Kubernetes cluster. In order to do so, we created the following Dockerfile;
And a Helm chart with the following values;
However, when we deploy this - the following FATAL error occurs;
Looking at this file, https://github.com/opsgenie/oec/blob/master/queue/processor.go - it expects some kind of token credentials in /v2/integrations/oec/credentials ? but this file is nowhere to be found nor do i see any references to it in the code or documentation.
What are we missing here? Thank you
The text was updated successfully, but these errors were encountered: