Does Tyk Analytics depend on Mongo or not?


#1

According to
https://tyk.io/docs/tyk-api-gateway-v-2-0/installation-options-setup/install-tyk-pro-edition-on-ubuntu/
I configured Tyk Dashboard following the command,
sudo /opt/tyk-dashboard/install/setup.sh --listenport=3000 --redishost=localhost --redisport=6379 --mongo=mongodb://127.0.0.1/tyk_analytics --tyk_api_hostname=127.0.0.1 --tyk_node_hostname=http://127.0.0.1 --tyk_node_port=8080 --portal_root=/portal --domain=“dashboard.tyk-local.com

However,
https://tyk.io/docs/tyk-api-gateway-v-2-0/upgrading-to-tyk-v2-0/ indicates that MongoDB is no longer a dependency for the gateway,
where
https://tyk.io/docs/tyk-dashboard-v1-0/ indicates that MongoDB is a dependency for the dashboard

I tend to assume the below. Please correct me if I am wrong (or if the pages I referred to are outdated).

  1. Tyk Gateway 2.0 does not depend on Mongo.
  2. Tyk Dashboard 1.0 depends on Mongo

Regards,
Pradeeban.


#2

The gateway, used in isolation, does not require mongoDB
The gateway, used with the dashboard, requires mongoDB, because the dashboard requires mongoDB.


#3

Is this still the case or can you now use ElasticSearch in place of Mongo? The docs are seemingly contradictory on this.


#4

This is stil the case.

We’re pretty clear: Tyk Pro (dashboard) requires mongo.

However, you can use ES for your own data aggregation, Tyk Pump will send data to it as well as Mongo (and segment io and statsd and in fact anything you want to write a driver for, there’s quite a few new aggregators in our dev branch)


#5

Does Tyk Gateway have a direct dependency on MongoDb? I understand that a Tyk Pro install depends on Mongo because the dashboard service uses it however looking at deployment diagram there is no relationship between Gateway and Mongo.

The template configuration file that is installed with Tyk gateway has the following sections defined:
.analytics_config.mongo_url
.analytics_config.mongo_db_name

However there is no mention of this in the Gateway configuration reference

Thanks


#6

Gateways before v2.0 had a direct dependency, which is why the config element is still there. It will be deprecated soon.