We haven't received any data!

Torbjörn

Posted on
Mar 26 2013

Have tried to send my exceptions with Raygun4Net and the api answer is "202". However, on my dashboard i only see the message "We haven't received any data!". The API-key is provided in the http request and looks ok.

The HTTP request looks like this:

POST https://api.raygun.io/entries HTTP/1.1
X-ApiKey: xxxxxxx
Host: api.raygun.io
Content-Length: 777
Expect: 100-continue
Connection: Keep-Alive

{"OccurredOn":"2013-03-26T12:19:28.5347126Z","Details":{"MachineName":"XXXXXX","Version":"Not supplied","Error":{"Data":[],"ClassName":"System.ApplicationException","Message":"ApplicationException: Testing","StackTrace":[{"LineNumber":0,"FileName":"none"}]},"Environment":{"ProcessorCount":8,"OSVersion":"6.1.7601.65536","WindowBoundsWidth":1200,"WindowBoundsHeight":3840,"Cpu":"Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz","Architecture":"x86","TotalPhysicalMemory":8148,"AvailablePhysicalMemory":1239,"TotalVirtualMemory":2047,"AvailableVirtualMemory":1328,"DiskSpaceFree":[264.38608551025391,689.0936279296875],"Locale":"Swedish (Sweden)"},"Client":{"Name":"Raygun4Net","Version":"1.0.4.0","ClientUrl":"https://github.com/MindscapeHQ/raygun4net"},"Tags":["Test","DB"]}}

What am I doing wrong?

Torbjörn

Posted on
Mar 27 2013

Now I see my data - three hours later.

Scott Alexander

Posted on
Mar 27 2013

I have observed similar delays recently. Previously the data showed up in seconds. Has there been a change in workflow? Should we no longer expect to see the data immediately? The "real-time data" is very important to us as we use it to get immediate feedback when shipping a new build, allowing us to react quickly to regressions.

John-Daniel Trask

Raygun

Posted on
Mar 27 2013

Hi Scott & Torbjörn and Michael,

Apologies for this - there was a slow down which we didn't foresee. We're currently in the process of building the test search cluster (for the search / filtering features we're working on for Raygun). It's taking a few days to build this up and checking on this we can see it's caused a slow down (no data is lost, just slower -- which is still not good, we like things that are fast!).

We're making some changes today to bring it back to real-time speeds. I've also paused the process related to the search to clear the backlog. We won't resume until we have cleared the backlog and have ensured it won't impact the update speed of your dashboards and data.

Sorry about that, we thought he had lowered the throughput to not cause this impact.

At peak the delay was approximately 3 hours, the queue is now getting cleared a lot faster and should be back to real time in the next hour or so. We're keeping a tight eye on the queue at present.

Kind regards,

John-Daniel Trask
Co-founder
Mindscape Limited

Reply