| Excerpt |
|---|
This page describes the third party tools (e.g. Jeager, Docker Repository, Splunk) used for e.g. log analysis and tracing. |
When hosting a BFF on the eHealth platform for either an employee or patient solution you will be given access to the following tools.
...
| Code Block | ||
|---|---|---|
| ||
{Vendor Short Name}-{Application Short Name}/* |
Deployment specified as code
The deployment and configuration is defined in a dedicated git repository for each BFF application.
...
A deployment pipeline is connected to this repository, following the outline described in Development and deployment cycle .
Docker Image hosting
Each BFF application is given a docker repository hosted on the eHealth Platform. It is only possible and allowed to deploy images to the different environments from this docker repository.
...
| Code Block |
|---|
{Vendor Short Name}-{Application Short Name}/bff |
Helm Chart repository
The vendor is given access to the helm chart repository hosted by the eHealth Platform.
This repository contains the only helm chart that the vendor is allowed to use to deploy the BFF on the platform. The chart should be complete enough to run any BFF, with different configuration for values, health endpoints, resource usage etc.
See Helm Charts for more info about the chart.
Kubernetes namespace
All applications on the platform is hosted on Kubernetes. To enforce separation between BFF applications and to harden the security on the platform each BFF application will have it’s own Kubernetes namespace.
...
| Code Block |
|---|
{Vendor Short Name}-{Application Short Name} |
Central Logging
The vendor is given access to a central log collection where you can see any logs, audits and metrics collected from the BFF. The vendor will not have access to logs for the rest of the platform services, or from other BFF applications.
...
See also Logging model for logging requirements.
Jaeger tracing
In the test environment the vendor is given access to a common tracing system where a call and the responcetimes response times of each involved service can be found. This is possible when all involved services has implemented the header propagation as described in Call Tracing
...
A GUI presenting the collected data for ie i.e. exttest car be accessed here https://jaeger.admin.exttest.ehealth.sundhed.dk/search