Knowledge Base

/Knowledge Base

Knowledge Base

3 08, 2019

Alerts, Issues and Notifications

By |2019-08-03T07:46:40+00:00August 3rd, 2019|Knowledge Base|0 Comments

See this blog to get insight on the way CopperEgg does alerts See this blog for configuration information and how-tos:

3 08, 2019

Understanding the detail behind CopperEgg Website Monitoring

By |2019-08-06T14:41:26+00:00August 3rd, 2019|Knowledge Base|0 Comments

CopperEgg provides Website, Web service and TCP port checking from its 9 global monitoring stations, as frequently as every 15 seconds.  We refer to one 'check' as a Probe; you can define all aspects of each of your probes within the Probes tab in the CopperEgg UI.  Data gathered for each of your probes includes response time, health and copperegg.  Check out this blog to understand what a Probe dashboard widget is telling you and the detail behind it:

3 08, 2019

Why do I want to tag my servers and probes?

By |2019-08-03T07:41:30+00:00August 3rd, 2019|Knowledge Base|0 Comments

Tagging is an important and simple way to do advanced functions in CopperEgg To tag a server, simply click on the details button (bottom right) on any dashboard widget. Then use the green + button to add a tag. Keep it simple, things like prod, web, api, dev, db, app may do the job just fine. Tags are used for: 1. Creating a correlated view of servers, probes and RUM web apps in the detail view when tagged the same, for example, web, prod, frontend, app, api, db, etc. 2. Filtering your dashboard to show only those system tagged "x" [...]

3 08, 2019

How to automatically set tags, label, and UUID when installing on a Windows server

By |2019-08-03T07:43:28+00:00August 3rd, 2019|Knowledge Base|0 Comments

Its easy to auto tag and label when installing the CopperEgg collector on a Windows server. Just append these parameters when you run the MSI at a command prompt RevealCloudSetup.msi /qbr APIKEY="apikey" TAGS="sql.web,prod" LABEL="my server" You can find your API key here: >Settings >Account Settings For some cases, specifying the UUID (unique identifier) may be useful, though only recommended when the MAC address is not a reliable unique identifier: RevealCloudSetup.msi /qbr APIKEY="apikey" UUID="server-name"

3 08, 2019

How do I setup my accounting dept to see my paid invoices or statements?

By |2019-08-03T04:19:59+00:00August 3rd, 2019|Knowledge Base|0 Comments

Admin users can navigate and retrieve the monthly billing statements, but some companies are hesitant to give someone in the accounting office, admin access. To solve this issue, simply create a user account for the person, (or alias) as an admin account, but use the tag restriction feature. Select a unique tag, that does not appear on any other server, probe or other object in your CopperEgg account. Then that person will not see any of the setup or running servers or probes in the account and can't accidentally "break" anything. Use a unique tag such as: TEqFNfxk I just created [...]

3 08, 2019

What units are used for network traffic?

By |2019-08-03T06:59:50+00:00August 3rd, 2019|Knowledge Base|0 Comments

We display and report network traffic in bytes per second. The Network traffic chart can be found by clicking the Details button on the server of interest. You'll find it immediately under the CPU chart. The units on the y-axis will depend on the amount of traffic recorded during the time covered by the chart.  Most often it will be KB/s, (Kilobytes per second); it could alternatively be displayed in MB/s or B/s (Megabytes per second, or Bytes per second). Tip:  KB/s is the common notation for Kilobytes per second; Kb/s is the notation used for Kilobits per second.

3 08, 2019

How does your collector communicate back from my server to the CopperEgg app and is it secure?

By |2019-08-03T06:56:47+00:00August 3rd, 2019|Knowledge Base|0 Comments

The CopperEgg collector, which is installed on your linux, windows, freebsd or mac OS server, initiates outbound communications.  In doing so there is typically no need to open firewall ports as the collector communicates outbound over ports 443 and 80.  The performance data is sent securely over port 443 using SSL. As long as the collector can communicate over the Internet, back to the CopperEgg app, it can monitor servers that are cloud based, hosted or on-prem, either virtual or physical.  We can even monitor virtual desktops in our unified dashboard. The collector sends performance information, such as CPU stats, % [...]