Created
April 18, 2016 19:56
-
-
Save gelirimlad/6964896c3037988bbe73f3991959a448 to your computer and use it in GitHub Desktop.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
=================== | |
Collector (v 5.7.3) | |
=================== | |
Status date: 2016-04-18 19:49:13 (388s ago) | |
Pid: 17 | |
Platform: Linux-4.2.2-coreos-r2-x86_64-with-debian-8.3 | |
Python Version: 2.7.11 | |
Logs: <stderr>, /var/log/datadog/collector.log | |
Clocks | |
====== | |
NTP offset: Unknown (No response received from 1.datadog.pool.ntp.org.) | |
System UTC time: 2016-04-18 19:55:43.295538 | |
Paths | |
===== | |
conf.d: /etc/dd-agent/conf.d | |
checks.d: /opt/datadog-agent/agent/checks.d | |
Hostnames | |
========= | |
ec2-hostname: ip-10-21-1-196.ec2.internal | |
local-ipv4: 10.21.1.196 | |
local-hostname: ip-10-21-1-196.ec2.internal | |
socket-hostname: ip-10-21-1-196.ec2.internal | |
public-hostname: ec2-54-87-225-110.compute-1.amazonaws.com | |
hostname: ip-10-21-1-196.ec2.internal | |
instance-id: i-b7a47b30 | |
public-ipv4: 54.87.225.110 | |
socket-fqdn: ip-10-21-1-196.ec2.internal | |
Checks | |
====== | |
clusterdb | |
--------- | |
- Collected 0 metrics, 0 events & 1 service check | |
postgres | |
-------- | |
- instance #0 [WARNING] | |
Warning: "dbname" parameter must be set when using the "relations" parameter. | |
- Collected 56 metrics, 0 events & 2 service checks | |
elastic | |
------- | |
- instance #0 [ERROR]: '503 Server Error: Service Unavailable: Back-end server is at capacity' | |
- instance #1 [ERROR]: '403 Client Error: Forbidden' | |
- Collected 0 metrics, 0 events & 3 service checks | |
ntp | |
--- | |
- Collected 0 metrics, 0 events & 1 service check | |
docker_daemon | |
------------- | |
- instance #0 [OK] | |
- Collected 89 metrics, 0 events & 2 service checks | |
http_check | |
---------- | |
- instance #0 [WARNING] | |
Warning: Skipping SSL certificate validation for https://pad.bn.co/status based on configuration | |
Warning: Skipping SSL certificate validation for https://image-resizer.bn.co/status based on configuration | |
Warning: Skipping SSL certificate validation for https://billing-claims-api.bn.co/status based on configuration | |
Warning: Skipping SSL certificate validation for https://targetinglibrary-api.bn.co/status based on configuration | |
Warning: Skipping SSL certificate validation for https://template-feeds-api.bn.co/status based on configuration | |
Warning: Skipping SSL certificate validation for https://sheets-api.bn.co/status based on configuration | |
Warning: Skipping SSL certificate validation for https://ubx-api.bn.co/status based on configuration | |
Warning: Skipping SSL certificate validation for https://auth-api.bn.co/status based on configuration | |
Warning: Skipping SSL certificate validation for https://spreadsheets-api.bn.co/status based on configuration | |
Warning: Skipping SSL certificate validation for https://custom-locations-api.bn.co/status based on configuration | |
Warning: Skipping SSL certificate validation for https://product-feeds-api.bn.co/status/ based on configuration | |
Warning: Skipping SSL certificate validation for https://signals.bn.co/status/ based on configuration | |
Warning: Skipping SSL certificate validation for https://post-creator-api.bn.co/status/ based on configuration | |
Warning: Skipping SSL certificate validation for https://optimize-api-shift.bn.co/ based on configuration | |
Warning: Skipping SSL certificate validation for https://thumbnails-api.bn.co/status/ based on configuration | |
Warning: Skipping SSL certificate validation for https://facebook-tools-api.bn.co/status/ based on configuration | |
Warning: Skipping SSL certificate validation for https://files-api.bn.co/status/ based on configuration | |
Warning: Skipping SSL certificate validation for https://billing-api.bn.co/status/ based on configuration | |
Warning: Skipping SSL certificate validation for https://scheduler.bn.co/status/ based on configuration | |
Warning: Skipping SSL certificate validation for https://integrations-api.bn.co/status/ based on configuration | |
Warning: Skipping SSL certificate validation for https://platform-api.bn.co/status/ based on configuration | |
Warning: Skipping SSL certificate validation for https://posts-api.bn.co/status/ based on configuration | |
Warning: Skipping SSL certificate validation for https://video-thumbnails-api.bn.co/status/ based on configuration | |
Warning: Skipping SSL certificate validation for https://hailstone-api.bn.co/ based on configuration | |
Warning: Skipping SSL certificate validation for https://image-transformer.bn.co/status based on configuration | |
Warning: Skipping SSL certificate validation for https://file-uploads-api.bn.co/status/ based on configuration | |
Warning: Skipping SSL certificate validation for https://oauth.bn.co/status/ based on configuration | |
Warning: Skipping SSL certificate validation for https://oracle-srm.bn.co/status/ based on configuration | |
Warning: Skipping SSL certificate validation for https://integrations2.bn.co/status/ based on configuration | |
Warning: Skipping SSL certificate validation for https://hosted-feeds-api.bn.co/status/ based on configuration | |
Warning: Skipping SSL certificate validation for https://billing-claims-api.optorb.com/status/ based on configuration | |
Warning: Skipping SSL certificate validation for https://sheets-api.optorb.com/status/ based on configuration | |
Warning: Skipping SSL certificate validation for https://targetinglibrary-api.bnservers.com/status/ based on configuration | |
Warning: Skipping SSL certificate validation for https://template-feeds-api.optorb.com/status/ based on configuration | |
Warning: Skipping SSL certificate validation for https://product-feeds-api.optorb.com/status/ based on configuration | |
Warning: Skipping SSL certificate validation for https://media-library-api.optorb.com/status based on configuration | |
Warning: Skipping SSL certificate validation for https://pad.optorb.com/status/ based on configuration | |
Warning: Skipping SSL certificate validation for https://optimize-api-qa.bnservers.com/ based on configuration | |
Warning: Skipping SSL certificate validation for https://hosted-feeds-api.optorb.com/status/ based on configuration | |
Warning: Skipping SSL certificate validation for https://thumbnails-api.optorb.com/status/ based on configuration | |
Warning: Skipping SSL certificate validation for https://integrations-api.optorb.com/status/ based on configuration | |
Warning: Skipping SSL certificate validation for https://sirens-api-qa.bnservers.com/status/ based on configuration | |
Warning: Skipping SSL certificate validation for https://image-resizer.optorb.com/status based on configuration | |
Warning: Skipping SSL certificate validation for https://billing-api.optorb.com/status/ based on configuration | |
Warning: Skipping SSL certificate validation for https://file-uploads-api.optorb.com/status/ based on configuration | |
Warning: Skipping SSL certificate validation for https://scheduler-qa.bnservers.com/status/ based on configuration | |
Warning: Skipping SSL certificate validation for https://files-api.optorb.com/status/ based on configuration | |
Warning: Skipping SSL certificate validation for https://post-creator-api.optorb.com/status/ based on configuration | |
Warning: Skipping SSL certificate validation for https://posts-api.optorb.com/status/ based on configuration | |
Warning: Skipping SSL certificate validation for https://video-thumbnails-api.optorb.com/status/ based on configuration | |
Warning: Skipping SSL certificate validation for https://image-transformer.optorb.com/status based on configuration | |
Warning: Skipping SSL certificate validation for https://integrations2.optorb.com/status/ based on configuration | |
Warning: Skipping SSL certificate validation for https://spreadsheets-api.optorb.com/status/ based on configuration | |
Warning: Using events for service checks is deprecated in favor of monitors and will be removed in future versions of the Datadog Agent. | |
Warning: Using events for service checks is deprecated in favor of monitors and will be removed in future versions of the Datadog Agent. | |
Warning: Using events for service checks is deprecated in favor of monitors and will be removed in future versions of the Datadog Agent. | |
Warning: Using events for service checks is deprecated in favor of monitors and will be removed in future versions of the Datadog Agent. | |
Warning: Using events for service checks is deprecated in favor of monitors and will be removed in future versions of the Datadog Agent. | |
Warning: Using events for service checks is deprecated in favor of monitors and will be removed in future versions of the Datadog Agent. | |
Warning: Using events for service checks is deprecated in favor of monitors and will be removed in future versions of the Datadog Agent. | |
Warning: Using events for service checks is deprecated in favor of monitors and will be removed in future versions of the Datadog Agent. | |
Warning: Using events for service checks is deprecated in favor of monitors and will be removed in future versions of the Datadog Agent. | |
Warning: Using events for service checks is deprecated in favor of monitors and will be removed in future versions of the Datadog Agent. | |
Warning: Using events for service checks is deprecated in favor of monitors and will be removed in future versions of the Datadog Agent. | |
Warning: Using events for service checks is deprecated in favor of monitors and will be removed in future versions of the Datadog Agent. | |
Warning: Using events for service checks is deprecated in favor of monitors and will be removed in future versions of the Datadog Agent. | |
Warning: Using events for service checks is deprecated in favor of monitors and will be removed in future versions of the Datadog Agent. | |
Warning: Using events for service checks is deprecated in favor of monitors and will be removed in future versions of the Datadog Agent. | |
Warning: Using events for service checks is deprecated in favor of monitors and will be removed in future versions of the Datadog Agent. | |
Warning: Using events for service checks is deprecated in favor of monitors and will be removed in future versions of the Datadog Agent. | |
Warning: Using events for service checks is deprecated in favor of monitors and will be removed in future versions of the Datadog Agent. | |
Warning: Using events for service checks is deprecated in favor of monitors and will be removed in future versions of the Datadog Agent. | |
Warning: Using events for service checks is deprecated in favor of monitors and will be removed in future versions of the Datadog Agent. | |
Warning: Using events for service checks is deprecated in favor of monitors and will be removed in future versions of the Datadog Agent. | |
Warning: Using events for service checks is deprecated in favor of monitors and will be removed in future versions of the Datadog Agent. | |
Warning: Using events for service checks is deprecated in favor of monitors and will be removed in future versions of the Datadog Agent. | |
Warning: Using events for service checks is deprecated in favor of monitors and will be removed in future versions of the Datadog Agent. | |
Warning: Using events for service checks is deprecated in favor of monitors and will be removed in future versions of the Datadog Agent. | |
Warning: Using events for service checks is deprecated in favor of monitors and will be removed in future versions of the Datadog Agent. | |
Warning: Using events for service checks is deprecated in favor of monitors and will be removed in future versions of the Datadog Agent. | |
Warning: Using events for service checks is deprecated in favor of monitors and will be removed in future versions of the Datadog Agent. | |
Warning: Using events for service checks is deprecated in favor of monitors and will be removed in future versions of the Datadog Agent. | |
Warning: Using events for service checks is deprecated in favor of monitors and will be removed in future versions of the Datadog Agent. | |
Warning: Using events for service checks is deprecated in favor of monitors and will be removed in future versions of the Datadog Agent. | |
Warning: Using events for service checks is deprecated in favor of monitors and will be removed in future versions of the Datadog Agent. | |
Warning: Using events for service checks is deprecated in favor of monitors and will be removed in future versions of the Datadog Agent. | |
Warning: Using events for service checks is deprecated in favor of monitors and will be removed in future versions of the Datadog Agent. | |
Warning: Using events for service checks is deprecated in favor of monitors and will be removed in future versions of the Datadog Agent. | |
Warning: Using events for service checks is deprecated in favor of monitors and will be removed in future versions of the Datadog Agent. | |
Warning: Using events for service checks is deprecated in favor of monitors and will be removed in future versions of the Datadog Agent. | |
Warning: Using events for service checks is deprecated in favor of monitors and will be removed in future versions of the Datadog Agent. | |
Warning: Using events for service checks is deprecated in favor of monitors and will be removed in future versions of the Datadog Agent. | |
Warning: Using events for service checks is deprecated in favor of monitors and will be removed in future versions of the Datadog Agent. | |
Warning: Using events for service checks is deprecated in favor of monitors and will be removed in future versions of the Datadog Agent. | |
Warning: Using events for service checks is deprecated in favor of monitors and will be removed in future versions of the Datadog Agent. | |
Warning: Using events for service checks is deprecated in favor of monitors and will be removed in future versions of the Datadog Agent. | |
Warning: Using events for service checks is deprecated in favor of monitors and will be removed in future versions of the Datadog Agent. | |
Warning: Using events for service checks is deprecated in favor of monitors and will be removed in future versions of the Datadog Agent. | |
Warning: Using events for service checks is deprecated in favor of monitors and will be removed in future versions of the Datadog Agent. | |
Warning: Using events for service checks is deprecated in favor of monitors and will be removed in future versions of the Datadog Agent. | |
Warning: Using events for service checks is deprecated in favor of monitors and will be removed in future versions of the Datadog Agent. | |
Warning: Using events for service checks is deprecated in favor of monitors and will be removed in future versions of the Datadog Agent. | |
Warning: Using events for service checks is deprecated in favor of monitors and will be removed in future versions of the Datadog Agent. | |
Warning: Using events for service checks is deprecated in favor of monitors and will be removed in future versions of the Datadog Agent. | |
Warning: Using events for service checks is deprecated in favor of monitors and will be removed in future versions of the Datadog Agent. | |
Warning: Using events for service checks is deprecated in favor of monitors and will be removed in future versions of the Datadog Agent. | |
Warning: Using events for service checks is deprecated in favor of monitors and will be removed in future versions of the Datadog Agent. | |
Warning: Using events for service checks is deprecated in favor of monitors and will be removed in future versions of the Datadog Agent. | |
Warning: Using events for service checks is deprecated in favor of monitors and will be removed in future versions of the Datadog Agent. | |
Warning: Using events for service checks is deprecated in favor of monitors and will be removed in future versions of the Datadog Agent. | |
Warning: Using events for service checks is deprecated in favor of monitors and will be removed in future versions of the Datadog Agent. | |
Warning: Using events for service checks is deprecated in favor of monitors and will be removed in future versions of the Datadog Agent. | |
Warning: Using events for service checks is deprecated in favor of monitors and will be removed in future versions of the Datadog Agent. | |
Warning: Using events for service checks is deprecated in favor of monitors and will be removed in future versions of the Datadog Agent. | |
Warning: Using events for service checks is deprecated in favor of monitors and will be removed in future versions of the Datadog Agent. | |
Warning: Using events for service checks is deprecated in favor of monitors and will be removed in future versions of the Datadog Agent. | |
Warning: Using events for service checks is deprecated in favor of monitors and will be removed in future versions of the Datadog Agent. | |
Warning: Using events for service checks is deprecated in favor of monitors and will be removed in future versions of the Datadog Agent. | |
Warning: Using events for service checks is deprecated in favor of monitors and will be removed in future versions of the Datadog Agent. | |
Warning: Using events for service checks is deprecated in favor of monitors and will be removed in future versions of the Datadog Agent. | |
Warning: Using events for service checks is deprecated in favor of monitors and will be removed in future versions of the Datadog Agent. | |
Warning: Using events for service checks is deprecated in favor of monitors and will be removed in future versions of the Datadog Agent. | |
Warning: Using events for service checks is deprecated in favor of monitors and will be removed in future versions of the Datadog Agent. | |
Warning: Using events for service checks is deprecated in favor of monitors and will be removed in future versions of the Datadog Agent. | |
Warning: Using events for service checks is deprecated in favor of monitors and will be removed in future versions of the Datadog Agent. | |
Warning: Using events for service checks is deprecated in favor of monitors and will be removed in future versions of the Datadog Agent. | |
Warning: Using events for service checks is deprecated in favor of monitors and will be removed in future versions of the Datadog Agent. | |
Warning: Using events for service checks is deprecated in favor of monitors and will be removed in future versions of the Datadog Agent. | |
Warning: Using events for service checks is deprecated in favor of monitors and will be removed in future versions of the Datadog Agent. | |
Warning: Using events for service checks is deprecated in favor of monitors and will be removed in future versions of the Datadog Agent. | |
Warning: Using events for service checks is deprecated in favor of monitors and will be removed in future versions of the Datadog Agent. | |
Warning: Using events for service checks is deprecated in favor of monitors and will be removed in future versions of the Datadog Agent. | |
Warning: Using events for service checks is deprecated in favor of monitors and will be removed in future versions of the Datadog Agent. | |
Warning: Using events for service checks is deprecated in favor of monitors and will be removed in future versions of the Datadog Agent. | |
Warning: Using events for service checks is deprecated in favor of monitors and will be removed in future versions of the Datadog Agent. | |
Warning: Using events for service checks is deprecated in favor of monitors and will be removed in future versions of the Datadog Agent. | |
Warning: Using events for service checks is deprecated in favor of monitors and will be removed in future versions of the Datadog Agent. | |
Warning: Using events for service checks is deprecated in favor of monitors and will be removed in future versions of the Datadog Agent. | |
Warning: Using events for service checks is deprecated in favor of monitors and will be removed in future versions of the Datadog Agent. | |
Warning: Using events for service checks is deprecated in favor of monitors and will be removed in future versions of the Datadog Agent. | |
Warning: Using events for service checks is deprecated in favor of monitors and will be removed in future versions of the Datadog Agent. | |
Warning: Using events for service checks is deprecated in favor of monitors and will be removed in future versions of the Datadog Agent. | |
Warning: Using events for service checks is deprecated in favor of monitors and will be removed in future versions of the Datadog Agent. | |
Warning: Using events for service checks is deprecated in favor of monitors and will be removed in future versions of the Datadog Agent. | |
Warning: Using events for service checks is deprecated in favor of monitors and will be removed in future versions of the Datadog Agent. | |
Warning: Using events for service checks is deprecated in favor of monitors and will be removed in future versions of the Datadog Agent. | |
Warning: Using events for service checks is deprecated in favor of monitors and will be removed in future versions of the Datadog Agent. | |
Warning: Using events for service checks is deprecated in favor of monitors and will be removed in future versions of the Datadog Agent. | |
Warning: Using events for service checks is deprecated in favor of monitors and will be removed in future versions of the Datadog Agent. | |
Warning: Using events for service checks is deprecated in favor of monitors and will be removed in future versions of the Datadog Agent. | |
Warning: Using events for service checks is deprecated in favor of monitors and will be removed in future versions of the Datadog Agent. | |
Warning: Using events for service checks is deprecated in favor of monitors and will be removed in future versions of the Datadog Agent. | |
Warning: Using events for service checks is deprecated in favor of monitors and will be removed in future versions of the Datadog Agent. | |
Warning: Using events for service checks is deprecated in favor of monitors and will be removed in future versions of the Datadog Agent. | |
Warning: Using events for service checks is deprecated in favor of monitors and will be removed in future versions of the Datadog Agent. | |
Warning: Using events for service checks is deprecated in favor of monitors and will be removed in future versions of the Datadog Agent. | |
Warning: Using events for service checks is deprecated in favor of monitors and will be removed in future versions of the Datadog Agent. | |
Warning: Using events for service checks is deprecated in favor of monitors and will be removed in future versions of the Datadog Agent. | |
Warning: Using events for service checks is deprecated in favor of monitors and will be removed in future versions of the Datadog Agent. | |
Warning: Using events for service checks is deprecated in favor of monitors and will be removed in future versions of the Datadog Agent. | |
Warning: Using events for service checks is deprecated in favor of monitors and will be removed in future versions of the Datadog Agent. | |
Warning: Using events for service checks is deprecated in favor of monitors and will be removed in future versions of the Datadog Agent. | |
Warning: Using events for service checks is deprecated in favor of monitors and will be removed in future versions of the Datadog Agent. | |
Warning: Using events for service checks is deprecated in favor of monitors and will be removed in future versions of the Datadog Agent. | |
Warning: Using events for service checks is deprecated in favor of monitors and will be removed in future versions of the Datadog Agent. | |
Warning: Using events for service checks is deprecated in favor of monitors and will be removed in future versions of the Datadog Agent. | |
Warning: Using events for service checks is deprecated in favor of monitors and will be removed in future versions of the Datadog Agent. | |
Warning: Using events for service checks is deprecated in favor of monitors and will be removed in future versions of the Datadog Agent. | |
Warning: Using events for service checks is deprecated in favor of monitors and will be removed in future versions of the Datadog Agent. | |
Warning: Using events for service checks is deprecated in favor of monitors and will be removed in future versions of the Datadog Agent. | |
Warning: Using events for service checks is deprecated in favor of monitors and will be removed in future versions of the Datadog Agent. | |
- instance #1 [OK] | |
- instance #2 [OK] | |
- instance #3 [WARNING] | |
Warning: Skipping SSL certificate validation for https://content-api.bn.co/status/ based on configuration | |
- instance #4 [WARNING] | |
Warning: Skipping SSL certificate validation for https://sentiment-analysis.bn.co/status/ based on configuration | |
Warning: Skipping SSL certificate validation for https://content-compatibility-api.bn.co/status/ based on configuration | |
- instance #5 [OK] | |
- instance #6 [WARNING] | |
Warning: Skipping SSL certificate validation for https://content-service.bn.co/ based on configuration | |
Warning: Skipping SSL certificate validation for https://content-authorization.bn.co/ based on configuration | |
- instance #7 [WARNING] | |
Warning: Skipping SSL certificate validation for https://media-library-api.bn.co/status based on configuration | |
- instance #8 [OK] | |
- instance #9 [OK] | |
- instance #10 [OK] | |
- instance #11 [OK] | |
- instance #12 [OK] | |
- instance #13 [OK] | |
- instance #14 [OK] | |
- instance #15 [OK] | |
- instance #16 [OK] | |
- instance #17 [OK] | |
- instance #18 [OK] | |
- instance #19 [OK] | |
- instance #20 [OK] | |
- instance #21 [OK] | |
- instance #22 [OK] | |
- instance #23 [OK] | |
- instance #24 [OK] | |
- instance #25 [OK] | |
- instance #26 [OK] | |
- instance #27 [OK] | |
- instance #28 [OK] | |
- instance #29 [OK] | |
- instance #30 [OK] | |
- instance #31 [OK] | |
- instance #32 [OK] | |
- instance #33 [OK] | |
- instance #34 [OK] | |
- instance #35 [OK] | |
- instance #36 [OK] | |
- instance #37 [OK] | |
- instance #38 [OK] | |
- instance #39 [OK] | |
- instance #40 [OK] | |
- instance #41 [OK] | |
- instance #42 [OK] | |
- instance #43 [OK] | |
- instance #44 [OK] | |
- instance #45 [OK] | |
- instance #46 [OK] | |
- instance #47 [OK] | |
- instance #48 [OK] | |
- instance #49 [OK] | |
- instance #50 [OK] | |
- instance #51 [OK] | |
- instance #52 [OK] | |
- instance #53 [OK] | |
- instance #54 [OK] | |
- instance #55 [OK] | |
- instance #56 [OK] | |
- instance #57 [OK] | |
- instance #58 [OK] | |
- instance #59 [OK] | |
- instance #60 [OK] | |
- instance #61 [OK] | |
- Collected 59 metrics, 0 events & 119 service checks | |
rabbitmq | |
-------- | |
- instance #0 [OK] | |
- Collected 1584 metrics, 0 events & 8 service checks | |
disk | |
---- | |
- instance #0 [OK] | |
- Collected 32 metrics, 0 events & 1 service check | |
content_service | |
--------------- | |
- Collected 0 metrics, 0 events & 1 service check | |
Emitters | |
======== | |
- http_emitter [OK] | |
=================== | |
Dogstatsd (v 5.7.3) | |
=================== | |
Status date: 2016-04-18 19:55:43 (0s ago) | |
Pid: 14 | |
Platform: Linux-4.2.2-coreos-r2-x86_64-with-debian-8.3 | |
Python Version: 2.7.11 | |
Logs: <stderr>, /var/log/datadog/dogstatsd.log | |
Flush count: 44 | |
Packet Count: 0 | |
Packets per second: 0.0 | |
Metric count: 1 | |
Event count: 0 | |
Service check count: 0 | |
=================== | |
Forwarder (v 5.7.3) | |
=================== | |
Status date: 2016-04-18 19:55:43 (0s ago) | |
Pid: 16 | |
Platform: Linux-4.2.2-coreos-r2-x86_64-with-debian-8.3 | |
Python Version: 2.7.11 | |
Logs: <stderr>, /var/log/datadog/forwarder.log | |
Queue Size: 481 bytes | |
Queue Length: 1 | |
Flush Count: 134 | |
Transactions received: 46 | |
Transactions flushed: 45 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment