diff --git a/README.md b/README.md index a06c568..4f78f20 100644 --- a/README.md +++ b/README.md @@ -7,12 +7,13 @@ This integration is last tested with Artifactory 7.71.11 and Xray 3.88.12 versio ## Table of Contents `Note! You must follow the order of the steps throughout Splunk Configuration` + 1. [Splunk Setup](#splunk-setup) 2. [JFrog Metrics Setup](#jfrog-metrics-setup) 3. [FluentD Installation](#fluentd-installation) - * [OS / Virtual Machine](#os--virtual-machine) - * [Docker](#docker) - * [Kubernetes Deployment with Helm](#kubernetes-deployment-with-helm) + * [OS / Virtual Machine](#os--virtual-machine) + * [Docker](#docker) + * [Kubernetes Deployment with Helm](#kubernetes-deployment-with-helm) 4. [Dashboards](#dashboards) 5. [Splunk Demo](#splunk-demo) 6. [References](#references) @@ -20,9 +21,10 @@ This integration is last tested with Artifactory 7.71.11 and Xray 3.88.12 versio ## Splunk Setup ### Splunkbase App + Install the `JFrog Log Analytics Platform` app from Splunkbase [here!](https://splunkbase.splunk.com/app/5023/) -``` text +```text 1. Download file from Splunkbase 2. Open Splunk web console as administrator 3. From homepage click on settings wheel in top right of Apps section @@ -30,46 +32,50 @@ Install the `JFrog Log Analytics Platform` app from Splunkbase [here!](https://s 5. Select download file from Splunkbase on your computer 6. Click upgrade 7. Click upload -``` +``` Restart Splunk post installation of App. -``` text +```text 1. Open Splunk web console as administrator 2. Click on Settings then Server Controls 3. Click on Restart -``` +``` Login to Splunk after the restart completes. Confirm the version is the latest version available in Splunkbase. ### Configure Splunk + Our integration uses the [Splunk HEC](https://dev.splunk.com/enterprise/docs/dataapps/httpeventcollector/) to send data to Splunk. Users will need to configure the HEC to accept data (enabled) and also create a new token. Steps are below. #### Create index jfrog_splunk -``` text + +```text 1. Open Splunk web console as administrator 2. Click on "Settings" in dropdown select "Indexes" 3. Click on "New Index" 4. Enter Index name as jfrog_splunk 5. Click "Save" -``` +``` #### Create index jfrog_splunk_metrics -``` text + +```text 1. Open Splunk web console as administrator 2. Click on "Settings" in dropdown select "Indexes" 3. Click on "New Index" 4. Enter Index name as jfrog_splunk_metrics 5. Select Index Data Type as Metrics 6. Click "Save" -``` +``` #### Configure new HEC token to receive Logs -``` text + +```text 1. Open Splunk web console as administrator 2. Click on "Settings" in dropdown select "Data inputs" 3. Click on "HTTP Event Collector" @@ -81,10 +87,11 @@ Users will need to configure the HEC to accept data (enabled) and also create a 9. Click on the green "Review" button 10. If good, Click on the green "Done" button 11. Save the generated token value -``` +``` #### Configure new HEC token to receive Metrics -``` text + +```text 1. Open Splunk web console as administrator 2. Click on "Settings" in dropdown select "Data inputs" 3. Click on "HTTP Event Collector" @@ -96,10 +103,12 @@ Users will need to configure the HEC to accept data (enabled) and also create a 9. Click on the green "Review" button 10. If good, Click on the green "Done" button 11. Save the generated token value -``` +``` ## JFrog Metrics Setup + For non Kubernetes-based installations, enable metrics in Artifactory, make the following configuration changes to the [Artifactory System YAML](https://www.jfrog.com/confluence/display/JFROG/Artifactory+System+YAML) + ```yaml shared: metrics: @@ -109,6 +118,7 @@ artifactory: metrics: enabled: true ``` + Once this configuration is done and the application is restarted, metrics will be available in Open Metrics Format Metrics are enabled by default in Xray. @@ -117,16 +127,17 @@ For Kubernetes-based installations, openMetrics is enabled in the helm install c ## Fluentd Installation ### OS / Virtual Machine + Ensure you have access to the Internet from VM. Recommended install is through fluentd's native OS based package installs: -| OS | Package Manager | Link | -|----------------|------------------------|------------------------------------------------------| -| CentOS/RHEL | Linux - RPM (YUM) | https://docs.fluentd.org/installation/install-by-rpm | -| Debian/Ubuntu | Linux - APT | https://docs.fluentd.org/installation/install-by-deb | -| MacOS/Darwin | MacOS - DMG | https://docs.fluentd.org/installation/install-by-dmg | -| Windows | Windows - MSI | https://docs.fluentd.org/installation/install-by-msi | -| Gem Install** | MacOS & Linux - Gem | https://docs.fluentd.org/installation/install-by-gem | +| OS | Package Manager | Link | +| ------------- | ------------------- | ---------------------------------------------------- | +| CentOS/RHEL | Linux - RPM (YUM) | https://docs.fluentd.org/installation/install-by-rpm | +| Debian/Ubuntu | Linux - APT | https://docs.fluentd.org/installation/install-by-deb | +| MacOS/Darwin | MacOS - DMG | https://docs.fluentd.org/installation/install-by-dmg | +| Windows | Windows - MSI | https://docs.fluentd.org/installation/install-by-msi | +| Gem Install** | MacOS & Linux - Gem | https://docs.fluentd.org/installation/install-by-gem | ```text ** For Gem based install, Ruby Interpreter has to be setup first, following is the recommended process to install Ruby @@ -156,6 +167,7 @@ gem install fluent-plugin-jfrog-metrics ``` #### Configure FluentD + We rely heavily on environment variables so that the correct log files are streamed to your observability dashboards. Ensure that you fill in the .env file with correct values. Download the .env file from [here](https://raw.githubusercontent.com/jfrog/log-analytics-splunk/master/jfrog.env) * **JF_PRODUCT_DATA_INTERNAL**: The environment variable JF_PRODUCT_DATA_INTERNAL must be defined to the correct location. For each JFrog service you will find its active log files in the `$JFROG_HOME//var/log` directory @@ -164,7 +176,7 @@ We rely heavily on environment variables so that the correct log files are strea * **SPLUNK_HEC_PORT**: Splunk HEC configured port * **SPLUNK_HEC_TOKEN**: Splunk HEC Token for sending logs to Splunk * **SPLUNK_METRICS_HEC_TOKEN**: Splunk HEC Token for sending metrics to Splunk -* **SPLUNK_INSECURE_SSL**: false for test environments only or if http scheme. +* **SPLUNK_INSECURE_SSL**: false for test environments only or if http scheme. * **JPD_URL**: Artifactory JPD URL of the format `http://` * **JPD_ADMIN_USERNAME**: Artifactory username for authentication * **JFROG_ADMIN_TOKEN**: Artifactory [Access Token](https://jfrog.com/help/r/how-to-generate-an-access-token-video/artifactory-creating-access-tokens-in-artifactory) for authentication @@ -178,72 +190,73 @@ source jfrog.env ``` ### Docker + `Note! These steps were not tested to work out of the box on MAC`
In order to run FluentD as a docker image to send the logs, violations and metrics data to splunk, the following commands needs to be executed on the host that runs the docker. 1. Check the docker installation is functional, execute command 'docker version' and 'docker ps'. - 2. Once the version and process are listed successfully, build the intended docker image for Splunk using the docker file, - * Download Dockerfile from [here](https://raw.githubusercontent.com/jfrog/log-analytics-splunk/master/docker-build/Dockerfile) to any directory which has write permissions. - + * Download Dockerfile from [here](https://raw.githubusercontent.com/jfrog/log-analytics-splunk/master/docker-build/Dockerfile) to any directory which has write permissions. 3. Download the docker.env file needed to run Jfrog/FluentD Docker Images for Splunk, - * Download docker.env from [here](https://raw.githubusercontent.com/jfrog/log-analytics-splunk/master/docker-build/docker.env) to the directory where the docker file was downloaded. + * Download docker.env from [here](https://raw.githubusercontent.com/jfrog/log-analytics-splunk/master/docker-build/docker.env) to the directory where the docker file was downloaded. For Splunk as the observability platform, execute these commands to setup the docker container running the FluentD installation -1. Execute - ```bash - docker build --build-arg SOURCE="JFRT" --build-arg TARGET="SPLUNK" -t . - ``` +1. Execute - Command example + ```bash + docker build --build-arg SOURCE="JFRT" --build-arg TARGET="SPLUNK" -t . + ``` - ```bash - docker build --build-arg SOURCE="JFRT" --build-arg TARGET="SPLUNK" -t jfrog/fluentd-splunk-rt . - ``` + Command example - The above command will build the docker image. + ```bash + docker build --build-arg SOURCE="JFRT" --build-arg TARGET="SPLUNK" -t jfrog/fluentd-splunk-rt . + ``` + The above command will build the docker image. 2. Fill the necessary information in the docker.env file - **JF_PRODUCT_DATA_INTERNAL**: The environment variable JF_PRODUCT_DATA_INTERNAL must be defined to the correct location. For each JFrog service you will find its active log files in the `$JFROG_HOME//var/log` directory - **SPLUNK_COM_PROTOCOL**: HTTP Scheme, http or https - **SPLUNK_HEC_HOST**: Splunk Instance URL - **SPLUNK_HEC_PORT**: Splunk HEC configured port - **SPLUNK_HEC_TOKEN**: Splunk HEC Token for sending logs to Splunk - **SPLUNK_METRICS_HEC_TOKEN**: Splunk HEC Token for sending metrics to Splunk - **SPLUNK_INSECURE_SSL**: false for test environments only or if http scheme - **JPD_URL: Artifactory JPD URL of the format `http://` - **JPD_ADMIN_USERNAME**: Artifactory username for authentication - **JFROG_ADMIN_TOKEN**: Artifactory [Access Token](https://jfrog.com/help/r/how-to-generate-an-access-token-video/artifactory-creating-access-tokens-in-artifactory) for authentication - **COMMON_JPD**: This flag should be set as true only for non-kubernetes installations or installations where JPD base URL is same to access both Artifactory and Xray (ex: https://sample_base_url/artifactory or https://sample_base_url/xray) + **JF_PRODUCT_DATA_INTERNAL**: The environment variable JF_PRODUCT_DATA_INTERNAL must be defined to the correct location. For each JFrog service you will find its active log files in the `$JFROG_HOME//var/log` directory + **SPLUNK_COM_PROTOCOL**: HTTP Scheme, http or https + **SPLUNK_HEC_HOST**: Splunk Instance URL + **SPLUNK_HEC_PORT**: Splunk HEC configured port + **SPLUNK_HEC_TOKEN**: Splunk HEC Token for sending logs to Splunk + **SPLUNK_METRICS_HEC_TOKEN**: Splunk HEC Token for sending metrics to Splunk + **SPLUNK_INSECURE_SSL**: false for test environments only or if http scheme + **JPD_URL: Artifactory JPD URL of the format `http://` + **JPD_ADMIN_USERNAME**: Artifactory username for authentication + **JFROG_ADMIN_TOKEN**: Artifactory [Access Token](https://jfrog.com/help/r/how-to-generate-an-access-token-video/artifactory-creating-access-tokens-in-artifactory) for authentication + **COMMON_JPD**: This flag should be set as true only for non-kubernetes installations or installations where JPD base URL is same to access both Artifactory and Xray (ex: https://sample_base_url/artifactory or https://sample_base_url/xray) +3. Execute -3. Execute - ```bash - docker run -it --name jfrog-fluentd-splunk-rt -v :/var/opt/jfrog/artifactory --env-file docker.env - ``` + ```bash + docker run -it --name jfrog-fluentd-splunk-rt -v :/var/opt/jfrog/artifactory --env-file docker.env + ``` - The should be an absolute path where the Jfrog Artifactory Logs folder resides, i.e for an Docker based Artifactory Installation, ex: /var/opt/jfrog/artifactory/var/logs on the docker host. + The should be an absolute path where the Jfrog Artifactory Logs folder resides, i.e for an Docker based Artifactory Installation, ex: /var/opt/jfrog/artifactory/var/logs on the docker host. - Command example + Command example - ```bash - docker run -it --name jfrog-fluentd-splunk-rt -v $JFROG_HOME/artifactory/var/:/var/opt/jfrog/artifactory --env-file docker.env jfrog/fluentd-splunk-rt - ``` + ```bash + docker run -it --name jfrog-fluentd-splunk-rt -v $JFROG_HOME/artifactory/var/:/var/opt/jfrog/artifactory --env-file docker.env jfrog/fluentd-splunk-rt + ``` ### Kubernetes Deployment with Helm + Recommended installation for Kubernetes is to utilize the helm chart with the associated values.yaml in this repo. + | Product | Example Values File | -|----------------|---------------------------------| +| -------------- | ------------------------------- | | Artifactory | helm/artifactory-values.yaml | | Artifactory HA | helm/artifactory-ha-values.yaml | | Xray | helm/xray-values.yaml | > [!WARNING] -> +> > The old docker registry `partnership-pts-observability.jfrog.io`, which contains older versions of this integration is now deprecated. We'll keep the existing docker images on this old registry until August 1st, 2024. After that date, this registry will no longer be available. Please `helm upgrade` your JFrog kubernetes deployment in order to pull images as specified on the above helm value files, from the new `releases-pts-observability-fluentd.jfrog.io` registry. Please do so in order to avoid `ImagePullBackOff` errors in your deployment once this registry is gone. Add JFrog Helm repository: @@ -276,22 +289,25 @@ export MASTER_KEY=$(openssl rand -hex 32) #### Artifactory ⎈: 1. Skip this step if you already have Artifactory installed. Else, install Artifactory using the command below - ```bash - helm upgrade --install artifactory jfrog/artifactory \ - --set artifactory.masterKey=$MASTER_KEY \ - --set artifactory.joinKey=$JOIN_KEY \ - --set artifactory.openMetrics.enabled=true \ - -n $INST_NAMESPACE --create-namespace - ``` + ```bash + helm upgrade --install artifactory jfrog/artifactory \ + --set artifactory.masterKey=$MASTER_KEY \ + --set artifactory.joinKey=$JOIN_KEY \ + --set artifactory.metrics.enabled=true \ + -n $INST_NAMESPACE --create-namespace + ``` + + :bulb: Metrics collection is disabled by default in Artifactory. Please make sure that you are following the above `helm upgrade` command to enable them in Artifactory by setting `artifactory.metrics.enabled=true`. For Artifactory versions <=7.86.x,please enable metrics by setting the flag `artifactory.openMetrics.enabled=true`
2. Create a secret for JFrog's admin token - [Access Token](https://jfrog.com/help/r/how-to-generate-an-access-token-video/artifactory-creating-access-tokens-in-artifactory) using any of the following methods - ```bash - kubectl create secret generic jfrog-admin-token --from-file=token= - - OR - - kubectl create secret generic jfrog-admin-token --from-literal=token= - ``` + + ```bash + kubectl create secret generic jfrog-admin-token --from-file=token= + + OR + + kubectl create secret generic jfrog-admin-token --from-literal=token= + ``` 3. For Artifactory installation, download the .env file from [here](https://github.com/jfrog/log-analytics-splunk/raw/master/helm/jfrog_helm.env). Fill in the jfrog_helm.env file with correct values. * **SPLUNK_COM_PROTOCOL**: HTTP Scheme, http or https @@ -304,57 +320,62 @@ export MASTER_KEY=$(openssl rand -hex 32) * **JPD_ADMIN_USERNAME**: Artifactory username for authentication * **COMMON_JPD**: This flag should be set as true only for non-kubernetes installations or installations where JPD base URL is same to access both Artifactory and Xray (ex: https://sample_base_url/artifactory or https://sample_base_url/xray) - Apply the .env files using the helm command below - - ```bash - source jfrog_helm.env - ``` + Apply the .env files using the helm command below + ```bash + source jfrog_helm.env + ``` 4. Postgres password is required to upgrade Artifactory. Run the following command to get the current password + ```bash POSTGRES_PASSWORD=$(kubectl get secret artifactory-postgresql -o jsonpath="{.data.postgresql-password}" | base64 --decode) ``` - 5. Upgrade Artifactory installation using the command below - ```bash - helm upgrade --install artifactory jfrog/artifactory \ - --set artifactory.joinKey=$JOIN_KEY \ - --set artifactory.openMetrics.enabled=true \ - --set databaseUpgradeReady=true --set postgresql.postgresqlPassword=$POSTGRES_PASSWORD --set nginx.service.ssloffload=true \ - --set splunk.host=$SPLUNK_HEC_HOST \ - --set splunk.port=$SPLUNK_HEC_PORT \ - --set splunk.logs_token=$SPLUNK_HEC_TOKEN \ - --set splunk.metrics_token=$SPLUNK_METRICS_HEC_TOKEN \ - --set splunk.com_protocol=$SPLUNK_COM_PROTOCOL \ - --set splunk.insecure_ssl=$SPLUNK_INSECURE_SSL \ - --set jfrog.observability.jpd_url=$JPD_URL \ - --set jfrog.observability.username=$JPD_ADMIN_USERNAME \ - --set jfrog.observability.common_jpd=$COMMON_JPD \ - -f helm/artifactory-values.yaml \ - -n $INST_NAMESPACE --create-namespace - ``` + + ```bash + helm upgrade --install artifactory jfrog/artifactory \ + --set artifactory.joinKey=$JOIN_KEY \ + --set databaseUpgradeReady=true --set postgresql.postgresqlPassword=$POSTGRES_PASSWORD --set nginx.service.ssloffload=true \ + --set splunk.host=$SPLUNK_HEC_HOST \ + --set splunk.port=$SPLUNK_HEC_PORT \ + --set splunk.logs_token=$SPLUNK_HEC_TOKEN \ + --set splunk.metrics_token=$SPLUNK_METRICS_HEC_TOKEN \ + --set splunk.com_protocol=$SPLUNK_COM_PROTOCOL \ + --set splunk.insecure_ssl=$SPLUNK_INSECURE_SSL \ + --set jfrog.observability.jpd_url=$JPD_URL \ + --set jfrog.observability.username=$JPD_ADMIN_USERNAME \ + --set jfrog.observability.common_jpd=$COMMON_JPD \ + -f helm/artifactory-values.yaml \ + -n $INST_NAMESPACE --create-namespace + ``` #### Artifactory-HA ⎈: + 1. For HA installation, please create a license secret on your cluster prior to installation. + ```bash kubectl create secret generic artifactory-license --from-file= ``` 2. Skip this step if you already have Artifactory installed. Else, install Artifactory using the command below - ```bash - helm upgrade --install artifactory-ha jfrog/artifactory-ha \ - --set artifactory.masterKey=$MASTER_KEY \ - --set artifactory.joinKey=$JOIN_KEY \ - --set artifactory.license.secret=artifactory-license \ - --set artifactory.license.dataKey=artifactory.cluster.license \ - --set artifactory.openMetrics.enabled=true \ - -n $INST_NAMESPACE --create-namespace - ``` + + ```bash + helm upgrade --install artifactory-ha jfrog/artifactory-ha \ + --set artifactory.masterKey=$MASTER_KEY \ + --set artifactory.joinKey=$JOIN_KEY \ + --set artifactory.license.secret=artifactory-license \ + --set artifactory.license.dataKey=artifactory.cluster.license \ + --set artifactory.metrics.enabled=true \ + -n $INST_NAMESPACE --create-namespace + ``` + + :bulb: Metrics collection is disabled by default in Artifactory-HA. Please make sure that you are following the above `helm upgrade` command to enable them in Artifactory by setting `artifactory.metrics.enabled=true`. For Artifactory versions <=7.86.x,please enable metrics by setting the flag `artifactory.openMetrics.enabled=true`
3. Create a secret for JFrog's admin token - [Access Token](https://jfrog.com/help/r/how-to-generate-an-access-token-video/artifactory-creating-access-tokens-in-artifactory) using any of the following methods + ```bash kubectl create secret generic jfrog-admin-token --from-file=token= - + OR - + kubectl create secret generic jfrog-admin-token --from-literal=token= ``` 4. Download the .env file from [here](https://github.com/jfrog/log-analytics-splunk/raw/master/helm/jfrog_helm.env). Fill in the jfrog_helm.env file with correct values. @@ -373,16 +394,17 @@ export MASTER_KEY=$(openssl rand -hex 32) ```bash source jfrog_helm.env - ``` + ``` 5. Postgres password is required to upgrade Artifactory. Run the following command to get the current password + ```bash POSTGRES_PASSWORD=$(kubectl get secret artifactory-ha-postgresql -o jsonpath="{.data.postgresql-password}" | base64 --decode) ``` 6. Upgrade Artifactory HA installation using the command below + ```bash helm upgrade --install artifactory-ha jfrog/artifactory-ha \ --set artifactory.joinKey=$JOIN_KEY \ - --set artifactory.openMetrics.enabled=true \ --set databaseUpgradeReady=true --set postgresql.postgresqlPassword=$POSTGRES_PASSWORD --set nginx.service.ssloffload=true \ --set splunk.host=$SPLUNK_HEC_HOST \ --set splunk.port=$SPLUNK_HEC_PORT \ @@ -400,6 +422,7 @@ export MASTER_KEY=$(openssl rand -hex 32) #### Xray ⎈: Create a secret for JFrog's admin token - [Access Token](https://jfrog.com/help/r/how-to-generate-an-access-token-video/artifactory-creating-access-tokens-in-artifactory) using any of the following methods if it doesn't exist + ```bash kubectl create secret generic jfrog-admin-token --from-file=token= @@ -425,7 +448,7 @@ Apply the .env files and then run the helm command below ```bash source jfrog_helm.env -``` +``` Generate a master key for xray @@ -455,6 +478,7 @@ helm upgrade --install xray jfrog/xray --set xray.jfrogUrl=$JPD_URL \ ## Dashboards ### Artifactory dashboard + JFrog Artifactory Dashboard is divided into multiple sections Application, Audit, Requests, Docker, System Metrics, Heap Metrics and Connection Metrics * **Application** - This section tracks Log Volume(information about different log sources) and Artifactory Errors over time(bursts of application errors that may otherwise go undetected) @@ -466,13 +490,15 @@ JFrog Artifactory Dashboard is divided into multiple sections Application, Audit * **Connection Metrics** - This section tracks Database connections and HTTP Connections ### Xray dashboard + JFrog Xray Dashboard is divided into three sections Logs, Violations and Metrics * **Logs** - This section provides a summary of access, service and traffic log volumes associated with Xray. Additionally, customers are also able to track various HTTP response codes, HTTP 500 errors, and log errors for greater operational insight -* **Violations** - This section provides an aggregated summary of all the license violations and security vulnerabilities found by Xray. Information is segment by watch policies and rules. Trending information is provided on the type and severity of violations over time, as well as, insights on most frequently occurring CVEs, top impacted artifacts and components. +* **Violations** - This section provides an aggregated summary of all the license violations and security vulnerabilities found by Xray. Information is segment by watch policies and rules. Trending information is provided on the type and severity of violations over time, as well as, insights on most frequently occurring CVEs, top impacted artifacts and components. * **Metrics** - This section tracks CPU usage, System Memory, Disk Usage, Heap Memory and Database Connections ### CIM Compatibility + Log data from JFrog platform logs is translated to pre-defined Common Information Models (CIM) compatible with Splunk. This compatibility enables new advanced features where users can search and access JFrog log data that is compatible with data models. For example ```text diff --git a/helm/artifactory-ha-values.yaml b/helm/artifactory-ha-values.yaml index e69fed8..9b11ec5 100644 --- a/helm/artifactory-ha-values.yaml +++ b/helm/artifactory-ha-values.yaml @@ -1,5 +1,8 @@ installerInfo: '{ "productId": "OnPremObservability-Splunk/1.0.1", "features": [ { "featureId": "ArtifactoryVersion/{{ default .Chart.AppVersion .Values.artifactory.image.version }}" }, { "featureId": "{{ if .Values.postgresql.enabled }}postgresql{{ else }}{{ .Values.database.type }}{{ end }}/0.0.0" }, { "featureId": "Platform/{{ default "kubernetes" .Values.installer.platform }}" }, { "featureId": "Channel/OnPremObservability-Splunk-Helm" } ] }' artifactory: + # For Artifactory versions <= 7.86.x please use artifactory.openMetrics.enabled instead of artifactory.metrics.enabled + metrics: + enabled: true customInitContainersBegin: | - name: "prepare-fluentd-conf-on-persistent-volume" image: {{ include "artifactory.getImageInfoByValue" (list . "initContainers") }} diff --git a/helm/artifactory-values.yaml b/helm/artifactory-values.yaml index 8b8e57e..3151d0a 100644 --- a/helm/artifactory-values.yaml +++ b/helm/artifactory-values.yaml @@ -1,5 +1,8 @@ installerInfo: '{ "productId": "OnPremObservability-Splunk/1.0.1", "features": [ { "featureId": "ArtifactoryVersion/{{ default .Chart.AppVersion .Values.artifactory.image.version }}" }, { "featureId": "{{ if .Values.postgresql.enabled }}postgresql{{ else }}{{ .Values.database.type }}{{ end }}/0.0.0" }, { "featureId": "Platform/{{ default "kubernetes" .Values.installer.platform }}" }, { "featureId": "Channel/OnPremObservability-Splunk-Helm" } ] }' artifactory: + # For Artifactory versions <= 7.86.x please use artifactory.openMetrics.enabled instead of artifactory.metrics.enabled + metrics: + enabled: true customInitContainersBegin: | - name: "prepare-fluentd-conf-on-persistent-volume" image: {{ include "artifactory.getImageInfoByValue" (list . "initContainers") }}