Installing analytics
Deploy the analytics CR to install the analytics subsystem in your API Connect deployment.
Before you begin
Now that you have a complete analytics CR file, double-check it for accuracy. In particular, verify that:
- No placeholder values remain in the analytics_cr.yaml file.
- You configured all the topology options that you plan to deploy.
- You configured appropriate volume size for storage.
Procedure
Results
Table 1 lists the pods that are expected in the three replica analytics deployment profile.
Expected | Pods | Note |
---|---|---|
3 | director | Always expected. |
3 | ingestion | Always expected. |
3 | mtls-gw | Always expected. |
3 | storage | Not expected if you disabled internal storage. |
3 | storage-os-master | Not expected if you disabled internal storage. Not expected if shared storage is configured. |
3 | osinit | Expected to be in completed state. |
1 | data-warehouse | Expected if backups are enabled. For information about analytics database backups, see configure analytics database backups. |
The one replica profile has 1 replica (instead of 3) of each pod.