I think it has something to do with something in the container itself - I checked and can see nginx
I threw up issue #244 for my problems running this
Found logs showing there is an issue updated my issue with the log
Howdy Iris Team! Is there a plan about moving Iris and other repos around Iris to Python 3 soon?
Perhaps there is a fork in the repo I did not see yet...
Ah,,, I see the branch now.
dwang159 had to revert the commit back because of some various issues with trying to upgrade to python3. At the moment only python2 (I think py2.7 to be precise) is supported.
I just want to make sure I am correct about the Oncall Notifier (i.e. reminder when users are coming up for a scheduled oncall shift) - it requires Iris integration, correct?
Looks like documentation for how to enable prometheus metrics is missing too... I'll figure that out and get a PR for the Docs
I reverted those commits since our example setup docs/docker images only worked on Python 2. We're currently running on the py3 branches in prod at Linkedin, but we need to make some changes to the docker images for it to run properly there.
Oncall notifier can use non-Iris messengers, but I'm not sure that any are currently implemented.
Expect to see a PR for documentation updates this evening (no rush) :)
Nevermind on the docs. Still figuring out how to enable prometheus metrics. I've edited the config to define metrics: prometheus but I can't figure out where to define the prom server port. I did review the metrics/prometheus.py module. How do I enable this?
Hi there, We have iris and oncall deployed in our org and were looking into adding functionality to handle incidents in more of an incident management system like OpsGenie; where there are multiple states like open, in-progress, closed, etc. Is this something that you folks at LinkedIn see value in working into the core application? For context, our incident workflow requires a little more incident state granularity, more than active being True or False.
Hey our team found a problem on master with Dockerfile, I opened a pull request however looks like there's a lot to sort out with the CircleCI builds.
main issue with Dockerfile was that it didn't copy the MANIFEST.in
Trying to setup iris, I am getting this error in terraform " Error: Error loading /home/user/Desktop/NOC/irisv2/iris-master/ops/terraform/iris.tf: Error reading config for aws_instance[iris-1]: parse error at 1:21: expected "}" but found float 0.0" has any one else faced this issue.
I was able to get the login screen, with mysql running as docker as well. How are users created?
Was able to add user as well thanks
Hi guys, I have a problem with the python Iris Client. It give me this error when I run the example: HMAC.update( b'' % (window, method, path, body)) TypeError: not all arguments converted during bytes formatting
Hi @dwang159 , how I have to lounch "make sender " command to test Iris Sender?
Attempting to handle Zabbix alerts in iris/oncall. For Zabbix, we can model after the Nagios plugin provided in the Git repo, however we'd first like to check with irisoncall/lobby here for any that have been-there/done-that with Zabbix -and- might be willing to share code (or even advise us differently).
Hi @dwang159 , @houqp . I'm using iris and oncall on aws cluster as a dockerized ecs container. Now i figured out that iris_sync_targets.py is not working in dockerized one. I can't sync the teams.. Any idea how to resolve it?