We also integrate with some of the leading cloud/hosting providers
check is a little different than the rest of the Circonus checks, instead of pulling information on a regular interval, accepts JSON payloads sent via HTTP PUT requests. During the configuration process you will be asked for 2 items, the target for this check is where the data will be coming from, and then a secret which will be used as part of your submission URL for added security
is a lightweight utility for local host monitoring that can be queried by tools such as nagios over http. One of the main design goals is portability: that resmon should require nothing more than a default install of Perl. Built with the philosophy that “we are smart because we are dumb,” that is, local requirements should be minimal to ease deployment on multiple platforms.
is an in-memory key-value store for small chunks of arbitrary data (strings, objects) from results of database calls, API calls, or page rendering.Memcached is simple yet powerful. Its simple design promotes quick deployment, ease of development, and solves many problems facing large data caches. Its API is available for most popular languages.
The NewRelic check allows you to import your NewRelic data into Circonus to allow easy correlation between services. If you need a NewRelic account click here
to get signed up for a free standard account.
nginx (engine x)
is an HTTP and reverse proxy server, as well as a mail proxy server.
is a simple NodeJS daemon, create by Etsy
that listens for messages on a UDP port. It parses the messages, extracts metrics data, and periodically flushes the data to Circonus. Note: This is available only in conjunction with a Circonus Enterprise Broker.
Cache is a web application accelerator also known as a caching HTTP reverse proxy. You install it in front of any server that speaks HTTP and configure it to cache the contents. Varnish Cache is really, really fast. It typically speeds up delivery with a factor of 300 – 1000x, depending on your architecture.One of the key features of Varnish Cache, in addition to its performance, is the flexibility of its configuration language, VCL. VCL enables you to write policies on how incoming requests should be handled. In such a policy you can decide what content you want to serve, from where you want to get the content and how the request or response should be altered.
is a free, very
fast and reliable solution offering high availability, load balancing, and proxying for TCP and HTTP-based applications. It is particularly suited for web sites crawling under very high loads while needing persistence or Layer7 processing. Circonus’ has built in support to monitor your HAProxy servers performance.
is a daemon which collects system performance statistics periodically and provides mechanisms to store the values in a variety of ways, for example in RRD files.
collectd gathers statistics about the system it is running on and stores this information. Those statistics can then be used to find current performance bottlenecks (i.e. performance analysis) and predict future system load (i.e. capacity planning).
The Collectd check allows you to run collectd on your hosts and send that data directly to Circonus. By default collectd sends data over UDP to a broker on port 25826. Because of the way collectd sends data, you cannot send this data to any of the Circonus Public Brokers.
The Broker, however, also provides an http/https endpoint to which collectd can submit via its write_http plugin.
The JMX technology provides the tools for building distributed, Web-based, modular and dynamic solutions for managing and monitoring devices, applications, and service-driven networks. By design, this standard is suitable for adapting legacy systems, implementing new management and monitoring solutions, and plugging into those of the future. Circonus’ built in support allows you to monitor your JMX Servers across your entire infrastructure.
is a networked resource monitoring tool that can help analyze resource trends performance problems. It is designed to be very plug and play. If you already have Munin nodes (or agents) running you can use these with Circonus. More here
allows you to remotely execute Nagios plugins on other Linux/Unix machines. If you have a specific plugin already installed on your hosts, you can continue using it with Circonus.
The Circonus Node Agent
(nad for short)will run scripts from the config directory; only from that and not subdirectories. The best practice it to write your scripts in subdirectories of the config dir and soft link to them to enable their execution.Some scripts distributed with nad need to be compiled (yes, they aren’t actually scripts, they are elf executables). Since not all programs can be compiled on all platforms, you need to go build them as needed. There are makefiles, pick and choose.If you write a set of scripts/programs, you can describe them in a .index.json file and they will be reported on when you run nad.
Windows Management Instrumentation
monitoring for your Windows® servers and apps is simple with the Circonus Windows Agent, and gives you amazing insight into real-time performance.
The Circonus Windows Agent pulls the metrics you want using the WMI interface, and reports them back to your Circonus account. It can be installed as a windows service running on port 34332, as a console services (running from an .exe) on port 34332, or as an IIS service running on port 80 from an existing IIS install.
The Circonus Windows Agent can be downloaded from your Circonus account when specifying a new Windows check/host.
We have seven different categories for Google Analytics: Visitors, Campaigns, Content, E-Commerce, Searches, Goals, and Events. Each of these allow you to pull a specific, related set of Google Analytics data for the site on which you have Google Analytics configured. Each category has a set of metrics associated with it. Each are described below. NOTE: These descriptions are all taken from the Google Analytics API documentation, which can be found here
: The total number of single page (or single engagement hit) sessions for your property.
: The number of entrances to your property measured as the first pageview in a session
: The number of exits from your property.
: The number of visitors whose visit to your property was marked as a first-time visit.
: The total number of pageviews for your property.
: How long a visitor spent on a particular page in seconds. Calculated by subtracting the initial view time for a particular page from the initial view time for a subsequent page. Thus, this metric does not apply to exit pages for your property.
: The total duration of visitor sessions represented in total seconds.
: Total number of visitors to your property for the requested time period.
: Counts the total number of sessions.
: The total number of times users have clicked on an ad to reach your property.
: Derived cost for the advertising campaign. The currency for this value is based on the currency that you set in your AdWords account.
: Cost to advertiser per click.
: Cost per thousand impressions.
: Click-through-rate for your ad. This is equal to the number of clicks divided by the number of impressions for your ad (e.g. how many times users clicked on one of your ads where that ad appeared).
: Total number of campaign impressions.
: The number of different (unique) pages within a session.
: The total revenue from purchased product items on your property.
: The total number of items purchased. For example, if users purchase 2 frisbees and 5 tennis balls, 7 items have been purchased.
: The total number of transactions.
: The total sale revenue provided in the transaction excluding shipping and tax.
: The total cost of shipping.
: The total amount of tax.
: The number of product sets purchased. For example, if users purchase 2 frisbees and 5 tennis balls from your site, 2 unique products have been purchased.
: The average number of subsequent page views made on your property after a use of your internal search feature.
: The visit duration to your property where a use of your internal search feature occurred.
: The number of exits on your site that occurred following a search result from your internal search feature.
: The total number of times a refinement (transition) occurs between internal search keywords within a session. For example if the sequence of keywords is: “shoes”, “shoes”, “pants”, “pants”, this metric will be one because the transition between “shoes” and “pants” is different.
: The total number of unique keywords from internal searches within a session. For example if “shoes” was searched for 3 times in a session, it will be only counted once.
searchVisits: The total number of sessions that included an internal search.
: The total number of completions for all goals defined for your profile.
: The total number of starts for all goals defined for your profile.
: The total numeric value for all goals defined for your profile.
: The total number of events for the profile, across all categories.
: The total number of unique events for the profile, across all categories.
: The total value of events for the profile.