Enable Default-Tenant logging
Set up central logging for the DuploCloud Default Tenant
Last updated
Was this helpful?
Set up central logging for the DuploCloud Default Tenant
Last updated
Was this helpful?
The Default Tenant in DuploCloud is the central management space for platform-wide resources and configurations, including monitoring and logging. Enabling logging in the Default Tenant deploys comprehensive Control Plane monitoring. This deployment uses OpenSearch and Kibana to retrieve and display log data. Once logging is enabled for the Default Tenant, you can enable logging for non-Default Tenants and configure logging per Tenant.
Central logging is typically set up during DuploCloud onboarding. Contact DuploCloud Support if you have questions about this process.
If needed, make changes to the Control Plane Configuration. You cannot modify the Control Plane Configuration after you set up logging.
If needed, customize Elastic Filebeat logging. Docker applications use stdout to write log files, collect logs, place them in the Host directory, mount them into Filebeat containers, and send them to AWS Elasticsearch. If you need to customize log collection using folders other than stdout, follow this procedure. Log collection cannot be customized after logging is set up.
From the Tenant list box at the top of the DuploCloud Portal, select the Default Tenant.
In the DuploCloud Portal, navigate to Administrator -> Observability -> Basic -> Settings, and select the Logging tab.
Click the Enable Logging link. The Enable Logging page displays.
In the Select Tenant list box, select Default.
In the Cert ARN field, enter the ARN certificate for the Default Tenant.
Find the ARN certificate by selecting the Default Tenant from the Tenant list box at the top of the DuploCloud Portal, navigating to Administrator -> Plans, selecting the Plan that matches your Infrastructure Name, clicking the Certificates tab, and copying the ARN from the Certificate ARN column.
Enter the number of days to retain logs in the Log Retention in Index (Days) field.
Click Submit. Data gathering takes about fifteen (15) minutes. When data gathering is complete, graphical logging data is displayed on the Logging tab.
When you enable logging for a Tenant, an Elastic Filebeat Service starts and begins log collection. The Elastic Filebeat Service must be running for log collection to occur.
To view the Filebeat Service, navigate to Kubernetes -> Services. To view the Filebeat containers, navigate to Kubernetes -> Containers. In the row of the container, click on the menu icon and select Logs.
Once logging is enabled for the Default Tenant, you can enable logging for other Tenants.
When you perform the steps above to configure logging, DuploCloud does the following:
An EC2 Host is added in the default Tenant, for example, duploservices-default-oc-diagnostics.
Services are added in the default Tenant, one for OpenSearch and one for Kibana. Both services are pinned to the EC2 host using allocation tags. Kibana is set up to point to ElasticSearch and exposed using an internal load balancer.
Security rules from within the internal network to port 443 are added in the default Tenant to allow log collectors that run on Tenant hosts to send logs to ElasticSearch.
A Filebeat service (filebeat-duploinfrasvc) is deployed for each Tenant where central logging is enabled.
The /var/lib/docker/Containers are mounted from the Host into the Filebeat container. The Filebeat container references ElasticSearch, which runs in the Default Tenant. Inside the container, Filebeat is configured so that every log line is added with metadata information consisting of the Tenant name, Service names, Container ID, and Hostname, enabling ease of search using these parameters with ElasticSearch.
