Could not log data point!

[userguy]

{
  "api_url": "http://status.file.test.com/api/v1/",
  "api_token": "rasdasdas",
  "monitors": [
    {
      "name": "API Servers Uptime",
      "url": "https://www.google.com/",
      "metric_id": null,
      "threshold": 80,
      "component_id": null,
      "expected_status_code": 200,
      "strict_tls": false
    }
  ],
  "insecure_api": true
}

These are the output

2016/02/13 21:28:38 /root/work/src/github.com/castawaylabs/cachet-monitor/main.go:13: Starting 1 monitors: 2016/02/13 21:28:38 /root/work/src/github.com/castawaylabs/cachet-monitor/main.go:15: API Servers Uptime: GET https://www.google.com & Expect HTTP 200 2016/02/13 21:28:38 /root/work/src/github.com/castawaylabs/cachet-monitor/main.go:21: 2016/02/13 21:28:39 /root/work/src/github.com/castawaylabs/cachet-monitor/cachet/monitor.go:84: https://www.google.com 0.00% Down at 1455379119. Threshold: 80.00% 2016/02/13 21:28:40 /root/work/src/github.com/castawaylabs/cachet-monitor/cachet/monitor.go:84: https://www.google.com 0.00% Down at 1455379120. Threshold: 80.00% 2016/02/13 21:28:41 /root/work/src/github.com/castawaylabs/cachet-monitor/cachet/monitor.go:84: https://www.google.com 0.00% Down at 1455379121. Threshold: 80.00% 2016/02/13 21:28:42 /root/work/src/github.com/castawaylabs/cachet-monitor/cachet/monitor.go:84: https://www.google.com 0.00% Down at 1455379122. Threshold: 80.00% 2016/02/13 21:28:43 /root/work/src/github.com/castawaylabs/cachet-monitor/cachet/monitor.go:84: https://www.google.com 0.00% Down at 1455379123. Threshold: 80.00% 2016/02/13 21:28:44 /root/work/src/github.com/castawaylabs/cachet-monitor/cachet/monitor.go:84: https://www.google.com 0.00% Down at 1455379124. Threshold: 80.00% 2016/02/13 21:28:45 /root/work/src/github.com/castawaylabs/cachet-monitor/cachet/monitor.go:84: https://www.google.com 0.00% Down at 1455379125. Threshold: 80.00% 2016/02/13 21:28:46 /root/work/src/github.com/castawaylabs/cachet-monitor/cachet/monitor.go:84: https://www.google.com 0.00% Down at 1455379126. Threshold: 80.00% 2016/02/13 21:28:47 /root/work/src/github.com/castawaylabs/cachet-monitor/cachet/monitor.go:84: https://www.google.com 0.00% Down at 1455379127. Threshold: 80.00% 2016/02/13 21:28:48 /root/work/src/github.com/castawaylabs/cachet-monitor/cachet/monitor.go:84: https://www.google.com 0.00% Down at 1455379128. Threshold: 80.00% 2016/02/13 21:28:49 /root/work/src/github.com/castawaylabs/cachet-monitor/cachet/monitor.go:84: https://www.google.com 0.00% Down at 1455379129. Threshold: 80.00%

AS per Your recommendation i checked with wireshark these are the reply

HTTP 167 CONNECT www.google.co.in:443 HTTP/1.1 HTTP 181 HTTP/1.1 200 Connection established TCP 66 52309 > http-alt [ACK] Seq=102 Ack=116 TCP 66 52309 > http-alt [ACK] Seq=255 Ack=2852 TCP 66 52309 > http-alt [ACK] Seq=255 Ack=4325 TCP 66 http-alt > 52309 [ACK] Seq=4325 Ack=336 TCP 66 52309 > http-alt [ACK] Seq=576 Ack=5756 TCP 66 52309 > http-alt [ACK] Seq=576 Ack=8308 TCP 66 52309 > http-alt [ACK] Seq=576 Ack=11044 TCP 66 52309 > http-alt [RST, ACK] Seq=607 TCP 54 52309 > http-alt [RST] Seq=576 Win=0 TCP 54 52309 > http-alt [RST] Seq=576 Win=0 HTTP 190 Continuation or non-HTTP traffic HTTP 726 Continuation or non-HTTP traffic TCP 66 52074 > http-alt [ACK] Seq=621 Ack=3301 TCP 74 52310 > http-alt [SYN] Seq=0 Win=14600 TCP 74 http-alt > 52310 [SYN, ACK] Seq=0 TCP 66 52310 > http-alt [ACK] Seq=1 Ack=1 HTTP 167 CONNECT www.google.co.in:443 HTTP/1.1 HTTP 181 HTTP/1.1 200 Connection established TCP 66 52310 > http-alt [ACK] Seq=102 Ack=116 TCP 66 52310 > http-alt [ACK] Seq=255 Ack=2852 TCP 66 52310 > http-alt [ACK] Seq=255 Ack=4325

What I am doing Wrong Here can you please Help

But Still i am not able to see the data written in dashboard ???

[matejkramny]

The cachet API isn't responding with HTTP 200.

Might you inspect the network with (eg wireshark) and see what it's responding with?

[userguy]

I have Updated my question .. Can you have a look at it ..

[jbrooksuk]

Cachet isn't doing anything here, is it? It looks like cachet-monitor is the issue.

[matejkramny]

@jbrooksuk I think the API might have updated and cachet-monitor hasn't caught up yet, or its a configuration error, or it might be something with the project itself. I have this open and will investigate

[matejkramny]

@userguy have you still got this issue?

Can you post more details if you do?

Scanning over the logs, everything seems fine.