1 6000110162 2015-08-21T13:01:45-04:00 6000171363 false Brokers 4 2015-10-30T11:00:31-04:00 1 1 2015-08-12T13:30:14-04:00 0 0 There are procedures for migrating checks, graphs, dashboards on one Broker to another. Migrating a Check The simplest use case for this procedure is that you have an existing check and you want to apply that same check from a different broker. This scenario can be handled through the Circonus UI in few short steps: Navigate to the check in question. Click the "view check details" link. Click the "change brokers and metrics" link. Select the additional broker(s) you desire by marking the check box(es). Migrating Everything It is also possible to perform a full broker migration, creating a wholesale copy of one broker to another broker, perhaps with targets in a different data center. This is a more complicated scenario, but you can use the API to perform the operation. First, identify the broker you want to copy. Use a command like this to read out all the bundles from that broker: GET /check_bundle?f_broker_has=/broker/<BROKER NUMBER> Then, do a substitution of the broker and any metric/check info. Finally, put the information back via the API, and the migration is complete. <div dir="ltr"> <div class="gmail_quote"><div dir="ltr"> <div>There are procedures for migrating checks, graphs, dashboards on one Broker to another.</div> <div><br></div> <div><b>Migrating a Check</b></div> <div></div> <div><br></div> <div>The simplest use case for this procedure is that you have an existing check and you want to apply that same check from a different broker. This scenario can be handled through the Circonus UI in few short steps:</div> <div> <ol> <li>Navigate to the check in question.<br> </li> <li>Click the "view check details" link.</li> <li>Click the "change brokers and metrics" link.</li> <li>Select the additional broker(s) you desire by marking the check box(es).</li> </ol> </div> <div><br></div> <div> <img src="https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/6003224682/original/edit-brokers.png?1439400614" alt="Inline image 2" width="562" height="296"><br> </div> <div><br></div> <div><b>Migrating Everything</b></div> <div><br></div> <div>It is also possible to perform a full broker migration, creating a wholesale copy of one broker to another broker, perhaps with targets in a different data center. This is a more complicated scenario, but you can use the API to perform the operation.</div> <div><br></div> <div>First, identify the broker you want to copy. Use a command like this<span> </span><span>to read out all the bundles from that broker</span><span>:</span> </div> <div><span><br></span></div> </div></div> </div> <blockquote style="margin: 0 0 0 40px; border: none; padding: 0px;"><div dir="ltr"><div class="gmail_quote"><div dir="ltr"><div><span>GET /check_bundle?f_broker_has=/broker/&lt;BROKER NUMBER&gt;</span></div></div></div></div></blockquote> <div dir="ltr"> <div class="gmail_quote"><div dir="ltr"> <div><br></div> <div>Then, do a substitution of the broker and any metric/check info. Finally, put the information back via the API, and the migration is complete.<br> </div> </div></div> <div class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"> <div> </div> </div></div></div></div></div></div> </div> 6000171363 115 6000041023 2015-12-07T16:32:24-05:00 6003235491 1 2 0 0 Migration of Checks, Graphs, and Dashboards between Brokers 2015-11-22T14:53:35-05:00 6002695175 1 2015-09-24T17:56:24-04:00 0 1 A broker is a server running a small piece of Circonus software that execute the checks that you define. For some check types, the broker software can speak directly to the monitored service, while others require an agent to be installed and configured on the host. You have access to a number of public brokers distributed around the world for you to use. When creating a check, you’ll need to make sure that the port listed below is reachable from the broker that you plan to use. You can find the broker hostname and IP from the Account->Brokers page in the Circonus UI (see Figure 1). Public brokers are often used to monitor publicly-accessible hosts or services. Alternatively, we offer the ability for you to run your own broker - an Enterprise Broker. The software can be run on a VM, AWS EC2 instance, or a physical server, and requires only a single SSL port (43191) back to our main Circonus systems. This is a perfect option for users who have large internal data centers with minimal external access. When connecting checks to Enterprise Brokers, you’ll need to make sure the ports listed for each check are reachable from this broker. When you log into your Circonus account, you will be able to see all the Brokers (Public and/or Enterprise) that are available on your account. Further information about installing, configuring, and system requirements can be found in the Circonus User's Manual. <p></p> <p>A broker is a server running a small piece of Circonus software that execute the checks that you define. For some check types, the broker software can speak directly to the monitored service, while others require an agent to be installed and configured on the host.</p> <p><br></p> <p></p> <p>You have access to a number of public brokers distributed around the world for you to use. When creating a check, you’ll need to make sure that the port listed below is reachable from the broker that you plan to use. You can find the broker hostname and IP from the Account-&gt;Brokers page in the Circonus UI (see Figure 1). Public brokers are often used to monitor publicly-accessible hosts or services.</p> <p><br></p> <p></p> <p>Alternatively, we offer the ability for you to run your own broker - an Enterprise Broker. The software can be run on a VM, AWS EC2 instance, or a physical server, and requires only a single SSL port (43191) back to our main Circonus systems. This is a perfect option for users who have large internal data centers with minimal external access. When connecting checks to Enterprise Brokers, you’ll need to make sure the ports listed for each check are reachable from this broker.</p> <p><br></p> <p></p> <p>When you log into your Circonus account, you will be able to see all the Brokers (Public and/or Enterprise) that are available on your account.</p> <p><br></p> <p></p> <p><img src="https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/6008240688/original/blob1446223089943.png?1446223086" class="inline-image" data-id="6008240688" data-height="477" style="height: 477px;"></p> <p><br></p> <p> </p> <p>Further information about installing, configuring, and system requirements can be found in the <a href="https://login.circonus.com/user/docs/Administration/Brokers" target="">Circonus User's Manual</a>. </p> <p><br></p> 6000171363 393 6000066935 2015-10-30T12:40:20-04:00 6003235491 1 2 0 1 What is a Circonus Broker? 2015-09-24T17:56:24-04:00 6003235491 1 2015-09-24T18:38:25-04:00 0 0 The Circonus Enterprise Broker (CEB) resides in your infrastructure and collects monitoring data from systems within your network. If you use Circonus Inside, a CEB communicates with the Core Circonus Inside software. If you use Circonus SaaS, a connection from the outside to the CEB (via a single port) is used to pull the raw data back to Circonus. All communications between Circonus and the CEB are SSL-encrypted and are limited to port 43191. The Circonus Enterprise Broker can run on RHEL5/6, CentOS 5/6, SmartOS, and OmniOS. We at Circonus, and a variety of our customers, run Brokers in a dedicated VM, or on physical HW with a minimum of 1GB of RAM and 20GB of local storage. <p>The Circonus Enterprise Broker (CEB) resides in your infrastructure and collects monitoring data from systems within your network. If you use Circonus Inside, a CEB communicates with the Core Circonus Inside software. If you use Circonus SaaS, a connection from the outside to the CEB (via a single port) is used to pull the raw data back to Circonus. All communications between Circonus and the CEB are SSL-encrypted and are limited to port 43191. </p> <p><br></p> <p> </p> <p>The Circonus Enterprise Broker can run on RHEL5/6, CentOS 5/6, SmartOS, and OmniOS. We at Circonus, and a variety of our customers, run Brokers in a dedicated VM, or on physical HW with a minimum of 1GB of RAM and 20GB of local storage. </p> <p><br></p> 6000171363 208 6000066962 2015-10-23T13:32:05-04:00 6003235491 2 2 0 0 What are the technical aspects of an Enterprise Broker? 2015-09-24T18:38:25-04:00 6003235491 1 2015-09-24T18:39:50-04:00 0 0 How do I update my Broker? On CentOS, use the yum update circonus-field-broker command. On OmniOS, use the pkg update field/broker command. It's that simple. <p><span style="font-family: 'Open Sans', 'Helvetica Neue', Helvetica, Arial, sans-serif; font-size: 14px;">How do I update my Broker?</span></p> <p><span style="font-family: 'Open Sans', 'Helvetica Neue', Helvetica, Arial, sans-serif; font-size: 14px;"><br></span></p> <p><span style="font-family: 'Open Sans', 'Helvetica Neue', Helvetica, Arial, sans-serif; font-size: 14px;">On CentOS, use the <b>yum update circonus-field-broker</b> command.</span></p> <p><span style="font-family: 'Open Sans', 'Helvetica Neue', Helvetica, Arial, sans-serif; font-size: 14px;"><br></span></p> <p><span style="font-family: 'Open Sans', 'Helvetica Neue', Helvetica, Arial, sans-serif; font-size: 14px;"> </span></p> <p><span style="font-family: 'Open Sans', 'Helvetica Neue', Helvetica, Arial, sans-serif; font-size: 14px;">On OmniOS, use the <b>pkg update field/broker</b> command.</span></p> <p><span style="font-family: 'Open Sans', 'Helvetica Neue', Helvetica, Arial, sans-serif; font-size: 14px;"><br></span></p> <p><span style="font-family: 'Open Sans', 'Helvetica Neue', Helvetica, Arial, sans-serif; font-size: 14px;">It's that simple.</span></p> 6000171363 140 6000066963 2015-10-23T13:34:09-04:00 6003235491 3 2 0 0 How do I update my Broker? 2015-09-24T18:39:50-04:00 6003235491 1 2015-09-24T18:40:45-04:00 0 0 Some users may wish to run pre-release or beta versions of the Enterprise Broker in order to try out new features or check bugfixes before they are promoted to general availability. To obtain pre-release packages, you will need to add the Circonus "pilot" repository to the system where the broker is running. Please note: Adopting the pilot repository means that you will get packages that have not received extensive production testing, but that updates will be released more frequently. Keep this fact in mind when deciding whether or not to use pilot packages. For example, to use pilot packages on a CentOS/RHEL system, add the following stanza to /etc/yum.repos.d/Circonus.repo: [circonus-pilot] name=Circonus - Pilot baseurl=http://pilot.circonus.net/centos/$releasever/x86_64/ enabled = 1 gpgcheck = 0 metadata_expire = 5m On OmniOS, you simply add another URL for the "circonus" publisher: pkg set-publisher -g http://pilot.circonus.net/omnios/ circonus The package names are the same, so you can update your existing broker package as you normally would. See "How do I update my Broker?" for details. To disable the pilot repo on CentOS/RHEL, set the "enabled" value to 0 for the circonus-pilot stanza. On OmniOS, disable the pilot repo by removing the URL: pkg set-publisher -G http://pilot.circonus.net/omnios/ circonus -esproul <p>Some users may wish to run pre-release or beta versions of the Enterprise Broker in order to try out new features or check bugfixes before they are promoted to general availability. To obtain pre-release packages, you will need to add the Circonus "pilot" repository to the system where the broker is running.</p> <p><br></p> <p><strong><em>Please note:</em></strong> Adopting the pilot repository means that you will get packages that have not received extensive production testing, but that updates will be released more frequently. Keep this fact in mind when deciding whether or not to use pilot packages.</p> <p><br></p> <p>For example, to use pilot packages on a CentOS/RHEL system, add the following stanza to /etc/yum.repos.d/Circonus.repo:</p> <pre style="font-family: Menlo, Monaco, Consolas, 'Courier New', monospace; margin-bottom: 20px; border: 1px solid rgba(0, 0, 0, 0.14902); background-color: rgb(245, 245, 245);"><ol style="padding-left: 0px; margin-top: 0px; margin-bottom: 0px; margin-left: 25px;"> <li> <span style="color: rgb(102, 102, 0);">[</span><span style="color: rgb(0, 0, 0);">circonus</span><span style="color: rgb(102, 102, 0);">-</span><span style="color: rgb(0, 0, 0);">pilot</span><span style="color: rgb(102, 102, 0);">]</span> </li> <li style="background: rgb(238, 238, 238);"> <span style="color: rgb(0, 0, 0);">name</span><span style="color: rgb(102, 102, 0);">=</span><span style="color: rgb(102, 0, 102);">Circonus</span><span style="color: rgb(0, 0, 0);"> </span><span style="color: rgb(102, 102, 0);">-</span><span style="color: rgb(0, 0, 0);"> </span><span style="color: rgb(102, 0, 102);">Pilot</span> </li> <li> <span style="color: rgb(0, 0, 0);">baseurl</span><span style="color: rgb(102, 102, 0);">=</span><a href="http://pilot.circonus.net/centos/%24releasever/x86_64/" style="color: rgb(59, 115, 185);"><span style="color: rgb(0, 0, 0);">http</span><span style="color: rgb(102, 102, 0);">:</span><span style="color: rgb(136, 0, 0);">//pilot.circonus.net/centos/$releasever/x86_64/</span></a> </li> <li style="background: rgb(238, 238, 238);"> <span style="color: rgb(0, 0, 0);">enabled </span><span style="color: rgb(102, 102, 0);">=</span><span style="color: rgb(0, 0, 0);"> </span><span style="color: rgb(0, 102, 102);">1</span> </li> <li> <span style="color: rgb(0, 0, 0);">gpgcheck </span><span style="color: rgb(102, 102, 0);">=</span><span style="color: rgb(0, 0, 0);"> </span><span style="color: rgb(0, 102, 102);">0</span> </li> <li style="background: rgb(238, 238, 238);"> <span style="color: rgb(0, 0, 0);">metadata_expire </span><span style="color: rgb(102, 102, 0);">=</span><span style="color: rgb(0, 0, 0);"> </span><span style="color: rgb(0, 102, 102);">5m</span> </li> </ol></pre> <p>On OmniOS, you simply add another URL for the "circonus" publisher:</p> <pre style="padding-top: 2px; padding-right: 2px; padding-left: 15px; font-family: Menlo, Monaco, Consolas, 'Courier New', monospace; margin-bottom: 20px; border: 1px solid rgba(0, 0, 0, 0.14902); background-color: rgb(245, 245, 245);"><ol style="padding-left: 0px; margin-top: 0px; margin-bottom: 0px; margin-left: 25px;"><li> <span style="color: rgb(0, 0, 0);">pkg </span><span style="color: rgb(0, 0, 136);">set</span><span style="color: rgb(102, 102, 0);">-</span><span style="color: rgb(0, 0, 0);">publisher </span><span style="color: rgb(102, 102, 0);">-</span><span style="color: rgb(0, 0, 0);">g </span><a href="http://pilot.circonus.net/omnios/" style="color: rgb(59, 115, 185);"><span style="color: rgb(0, 0, 0);">http</span><span style="color: rgb(102, 102, 0);">:</span><span style="color: rgb(136, 0, 0);">//pilot.circonus.net/omnios/</span></a><span style="color: rgb(136, 0, 0);"> circonus</span> </li></ol></pre> <p>The package names are the same, so you can update your existing broker package as you normally would. See "<a href="https://support.circonus.com/solution/articles/6000066963" style="color: rgb(59, 115, 185);">How do I update my Broker?</a>" for details.</p> <p><br></p> <p>To disable the pilot repo on CentOS/RHEL, set the "enabled" value to 0 for the circonus-pilot stanza.</p> <p><br></p> <p>On OmniOS, disable the pilot repo by removing the URL:</p> <pre style="padding-top: 2px; padding-right: 2px; padding-left: 15px; font-family: Menlo, Monaco, Consolas, 'Courier New', monospace; margin-bottom: 20px; border: 1px solid rgba(0, 0, 0, 0.14902); background-color: rgb(245, 245, 245);"><ol style="padding-left: 0px; margin-top: 0px; margin-bottom: 0px; margin-left: 25px;"><li> <span style="color: rgb(0, 0, 0);">pkg </span><span style="color: rgb(0, 0, 136);">set</span><span style="color: rgb(102, 102, 0);">-</span><span style="color: rgb(0, 0, 0);">publisher </span><span style="color: rgb(102, 102, 0);">-</span><span style="color: rgb(0, 0, 0);">G </span><a href="http://pilot.circonus.net/omnios/" style="color: rgb(59, 115, 185);"><span style="color: rgb(0, 0, 0);">http</span><span style="color: rgb(102, 102, 0);">:</span><span style="color: rgb(136, 0, 0);">//pilot.circonus.net/omnios/</span></a><span style="color: rgb(136, 0, 0);"> circonus</span> </li></ol></pre> <p>-esproul</p> 6000171363 126 6000066964 2015-10-23T13:42:50-04:00 6003235491 4 2 0 0 Brokers - How to get pre-release packages 2015-09-24T18:40:45-04:00 6003235491 1 2015-09-24T19:13:01-04:00 0 0 Can new lua scripts be added to a broker in order to create a new check? In short, yes. Instructions for configuring a custom module with Reconnoiter can be found in the Circonus User Manual and additional information can be found in the Reconnoiter Manual which is also available for public viewing from OmniTI Labs. <p style="margin-bottom: 10px; font-family: 'Open Sans', 'Helvetica Neue', Helvetica, Arial, sans-serif; font-size: 14px;">Can new lua scripts be added to a broker in order to create a new check?</p> <p style="margin-bottom: 10px; font-family: 'Open Sans', 'Helvetica Neue', Helvetica, Arial, sans-serif; font-size: 14px;"><span>In short, yes. Instructions for configuring a custom module with Reconnoiter can be found in the </span><a href="https://login.circonus.com/user/docs/Administration/Brokers#ConfiguringaCustomModulewithReconnoiter">Circonus User Manual</a><span> and additional information can be found in the </span><a href="https://login.circonus.com/resources/reconnoiter/">Reconnoiter Manual</a><span> which is also available for public viewing from </span><a href="https://labs.omniti.com/labs/reconnoiter/docs/">OmniTI Labs</a><span>.</span></p> 6000171363 65 6000066974 2015-11-19T15:51:42-05:00 6003235491 5 2 0 0 Is there documentation available on adding custom lua checks to brokers? 2015-09-24T19:13:01-04:00 6003235491