I don't see errors in the panel. What should I check?

2 min read Updated: 03.09.2026

If the application has been connected but no events are showing up in the project, it's best not to start by changing code. First check the basic reporting path from the application to the endpoint.

1. Check the project token

The token identifies the project the data should reach. Make sure your application configuration uses the token that belongs to that particular environment.

The most common mistake is using a token from a different project, or leaving an old value in place after switching environments.

2. Check the private key

If the integration uses authentication, check the private key as well. Watch out for extra spaces, an incomplete value, or a key that has already been revoked.

3. Send a manual request

A direct HTTP request lets you separate a problem with the application from a problem with communication with the API.

bash

curl -i -X POST \
"https://dockray.io/api/v1/PROJECT_TOKEN/project" \
-H "Authorization: Bearer PROJECT_PRIVATE_KEY" \
-H "Content-Type: application/json" \
-d '{
    "exception": {
    "values": [{
        "type": "Test",
        "value": "DockRay connection test"
    }]
    }
}'

If the manual request works but the application's integration still isn't reporting errors, look for the problem in the configuration or in how the application captures exceptions.

4. Check outbound connections

Some hosting environments restrict outbound connections. If the application server can't reach the monitoring endpoint, the library won't be able to send the event either.

5. Check your quota

If the project has reached its event quota, further reports may not show up as new data. Check the quota usage in the panel before making changes to the integration.

6. Check the date range and filters

Sometimes data is being sent correctly but isn't visible because of active filters. Clear the date range, statuses, and other list filters, then check the most recent events.

If nothing still works

The most valuable information for further diagnosis is: the integration used and its version, the runtime environment, the API response code, and a log excerpt showing the attempt to send the event.

Don't send tokens, private keys, or other secrets, though. Their names and whether they're configured correctly are enough for diagnosis.