Unable to notify event on slack

Below are the steps followed to setup sentry
Also, enabled webhook integration and added slack incoming webhook url to it.
Also, added sentry app into our slack.
#########Git Clone
git clone https://github.com/getsentry/onpremise.git
cd onpremise/
make build

docker stop $(docker ps -a -q)
docker rm $(docker ps -a -q)

export SMTP_HOST=""
export USE_TLS="True"
export EMAIL_PORT=“587"
export EMAIL_USER=”“
export EMAIL_PASSWORD=”“
export EMAIL_BACKEND=“django.core.mail.backends.smtp.EmailBackend"
export EMAIL_HOST_PASSWORD=”“
export SENTRY_SERVER_EMAIL=””

export REPOSITORY="sentry-onpremise"
export SENTRY_SECRET_KEY=docker run \ --rm ${REPOSITORY} \ config generate-secret-key

#########POSTGRES
docker stop sentry-postgres
docker rm sentry-postgres
docker run -d --name sentry-postgres -e POSTGRES_PASSWORD=secret -e POSTGRES_USER=sentry postgres

#########REDIS
docker stop sentry-redis
docker rm sentry-redis
docker run -d --name sentry-redis redis:3.2-alpine

#########SMTP
docker stop sentry-smtp
docker rm sentry-smtp
docker run
–detach
–name sentry-smtp --env SENTRY_EMAIL_HOST=$SMTP_HOST --env SENTRY_EMAIL_PASSWORD=$EMAIL_PASSWORD --env SENTRY_EMAIL_USER=$EMAIL_USER --env SENTRY_EMAIL_PORT=$EMAIL_PORT --env SENTRY_EMAIL_USE_TLS=$USE_TLS --env SENTRY_SERVER_EMAIL=$SENTRY_SERVER_EMAIL --env EMAIL_HOST_PASSWORD=$EMAIL_HOST_PASSWORD --env EMAIL_BACKEND=$EMAIL_BACKEND
tianon/exim4

#########Upgrade
docker run -it --rm -e SENTRY_SECRET_KEY=$SENTRY_SECRET_KEY --env SENTRY_EMAIL_HOST=$SMTP_HOST --env SENTRY_EMAIL_PASSWORD=$EMAIL_PASSWORD --env SENTRY_EMAIL_USER=$EMAIL_USER --env SENTRY_EMAIL_PORT=$EMAIL_PORT --env SENTRY_EMAIL_USE_TLS=$USE_TLS --env SENTRY_SERVER_EMAIL=$SENTRY_SERVER_EMAIL --env EMAIL_HOST_PASSWORD=$EMAIL_HOST_PASSWORD --env EMAIL_BACKEND=$EMAIL_BACKEND
–link sentry-postgres:postgres --link sentry-redis:redis sentry upgrade

#########Cron
docker stop sentry-cron
docker rm sentry-cron
docker run
–detach
–name sentry-cron
–link sentry-redis:redis
–link sentry-postgres:postgres
–link sentry-smtp:smtp
–env SENTRY_SECRET_KEY=${SENTRY_SECRET_KEY} --env SENTRY_EMAIL_HOST=$SMTP_HOST --env SENTRY_EMAIL_PASSWORD=$EMAIL_PASSWORD --env SENTRY_EMAIL_USER=$EMAIL_USER --env SENTRY_EMAIL_PORT=$EMAIL_PORT --env SENTRY_EMAIL_USE_TLS=$USE_TLS --env SENTRY_SERVER_EMAIL=$SENTRY_SERVER_EMAIL --env EMAIL_HOST_PASSWORD=$EMAIL_HOST_PASSWORD --env EMAIL_BACKEND=$EMAIL_BACKEND
${REPOSITORY}
run cron

#########WORKERS
docker stop sentry-worker
docker rm sentry-worker
docker run
–detach
–name sentry-worker
–link sentry-redis:redis
–link sentry-postgres:postgres
–link sentry-smtp:smtp
–env SENTRY_SECRET_KEY=${SENTRY_SECRET_KEY} --env SENTRY_EMAIL_HOST=$SMTP_HOST --env SENTRY_EMAIL_PASSWORD=$EMAIL_PASSWORD --env SENTRY_EMAIL_USER=$EMAIL_USER --env SENTRY_EMAIL_PORT=$EMAIL_PORT --env SENTRY_EMAIL_USE_TLS=$USE_TLS --env SENTRY_SERVER_EMAIL=$SENTRY_SERVER_EMAIL --env EMAIL_HOST_PASSWORD=$EMAIL_HOST_PASSWORD --env EMAIL_BACKEND=$EMAIL_BACKEND
${REPOSITORY}
run worker

#########WEB
docker stop sentry-web
docker rm sentry-web
docker run
–detach
–name sentry-web
-p 9000:9000
–link sentry-redis:redis
–link sentry-postgres:postgres
–link sentry-smtp:smtp --env SENTRY_EMAIL_HOST=$SMTP_HOST --env SENTRY_EMAIL_PASSWORD=$EMAIL_PASSWORD --env SENTRY_EMAIL_USER=$EMAIL_USER --env SENTRY_EMAIL_PORT=$EMAIL_PORT --env SENTRY_EMAIL_USE_TLS=$USE_TLS --env SENTRY_SERVER_EMAIL=$SENTRY_SERVER_EMAIL --env EMAIL_HOST_PASSWORD=$EMAIL_HOST_PASSWORD --env EMAIL_BACKEND=$EMAIL_BACKEND
–env SENTRY_SECRET_KEY=${SENTRY_SECRET_KEY}
${REPOSITORY}
run web

#########Sentry-Slack
docker exec -it sentry-web pip install sentry-slack; docker exec -it sentry-worker pip install sentry-slack; docker exec -it sentry-cron pip install sentry-slack;

Hey @murtuzamvista, this isn’t how you’d install the Slack plugin. What you did would never work. The plugin needs to get compiled into the container at build time.

You can do this by adding it to your requirements.txt file, then re-running make build.

Something like:

https://github.com/getsentry/sentry-slack/archive/master.zip

Should be sufficient in requirements.txt.

Thanks bro, this worked for me like a charm.

But I am unable to raise any event using RAILS error-tracking. Any
hints/suggestions would be very helpful.
It works with PYTHON properly.