[jira] [Commented] (INFRA-6380) Get circonus in "production" and nagios RIP.

["jan iversen (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/INFRA-6380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13684632#comment-13684632 ] 

jan iversen commented on INFRA-6380:
------------------------------------

Removed HTTPD/HTTPDS/VIEWVC checks, since nobody really wants them at the moment. And cleaned configuration, changed timeout, wait times so we are down to 2 alerts (which gmcdonald woulld solve, by opening a firewall)

Next step is to change the shell script controlling the special monitoring scripts with a python program.


                
> Get circonus in "production" and nagios RIP.
> --------------------------------------------
>
>                 Key: INFRA-6380
>                 URL: https://issues.apache.org/jira/browse/INFRA-6380
>             Project: Infrastructure
>          Issue Type: Task
>      Security Level: public(Regular issues) 
>          Components: Website
>         Environment: circonus server, status.a.o , infrabot (asfbot)
>            Reporter: jan iversen
>
> We are now at a state, where circonus has been shown on a "proof concept" basis. Circonus monitors the same hosts/vms/services (incl. special services like ldap) as nagios, and even more.
> can we please use this ticket to assemble all outstandings in form of comments, so we can solve them one by one.
> status:
> - Config is currently in review (danielsh)
> - Thx to Humbedooh, we have a proposal for a new status.a.o
> - Special checks are implemented as a cron controlled bash (config changes are manual)
> - generate.py, uploads any configuration changes to circonus server.
> - circonus-broker runs perfect
> - new vm for new status.a.o, infrabot is being configured (see other jira)
> I have not included future plans here, target for this jira is solely to get circonus operational.
> rgds
> jan I.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira