PHP error logs were successfully sent to Sentry but on the Sentry Dashboard no logs showed -

what reasons why sentry dashboard not being updated though errors sent?

i've tried simulating error , logging whole process in raven library getting exception sending sentry. raven returned 200 http code (success) when checked sentry dashboard logs empty.

our raven version 0.9.0

update:

i've tried raven cli tester shown here, send exception no logs showed in sentry dashboard.

update:

fixed reinstalling sentry , using new dsn. if there other solutions not require reinstall , use new dsn. feel free share answers.

if using sentry on-premise, can happen if worker processes not running or queue not backed up. official docs says:

sentry comes built-in queue process tasks in more asynchronous fashion. example when event comes in instead of writing database immediately, sends job queue request can returned right away, , background workers handle saving data.

and note, rely on celery library managing workers. running worker cli might solve issue :

$ sentry celery worker 

running service recommended, example configuration supervisor:

[program:sentry-worker] directory=/www/sentry/ command=/www/sentry/bin/sentry celery worker -l warning autostart=true autorestart=true redirect_stderr=true killasgroup=true 

sentry supports 2 primary brokers may adjusted depending on workload:

rabbitmq  , `redis` 

.

redis

the default broker redis, , work under situations. primary limitation using redis pending work must fit in memory.

broker_url = "redis://localhost:6379/0" 

if redis connection requires password authentication, need use following format:

broker_url = "redis://:password@localhost:6379/0" 

rabbitmq

if run high workload, or have concerns fitting pending workload in memory, rabbitmq ideal candidate backing sentry’s workers.

broker_url = "amqp://guest:guest@localhost:5672/sentry"