Influx configuration

Required privileges

The non-admin user, that is configured for Condition Monitoring ("cm.influxcm.userName" in cm helmchart), needs the following privilege per database: ALL (READ + WRITE)
For external InfluxDB you either need to create retention policies yourself or if possible give non-admin user additional CREATE RETENTION POLICY right.

Retention policies

Because of a bug in previous versions (before 4.0.0), the automatic configuration of retention policy durations for the Influx DB, which is created by non-admin user, was not correct. All configured retentions use the same from duration from rp_msm_raw.

With the update to version 4.0.0 the automatic configuration has been fixed, but this does not affect already existing Influx DBs. In order to change the retention policy durations some manual effort is necessary.

Recommended retention policy durations

Retention Name	Retention Duration	Helm Configuration
rp_event	180d	cm_local_influx_eventretentionpolicyduration
rp_msm_raw	7d	cm_local_influx_msmretentionpolicyduration
rp_msm_level1	45d	cm_local_influx_msmlevel1retentionpolicyduration
rp_msm_level2	90d	cm_local_influx_msmlevel2retentionpolicyduration
rp_msm_level3	180d	cm_local_influx_msmlevel3retentionpolicyduration
rp_msm_deferred	1d	cm_local_influx_msmdeferredretentionpolicyduration
rp_ppmp_meta_data	30d	cm_local_influx_eventretentionpolicyduration

Retention Name

Retention Duration

Helm Configuration

rp_event

180d

cm_local_influx_eventretentionpolicyduration

rp_msm_raw

cm_local_influx_msmretentionpolicyduration

rp_msm_level1

45d

cm_local_influx_msmlevel1retentionpolicyduration

rp_msm_level2

90d

cm_local_influx_msmlevel2retentionpolicyduration

rp_msm_level3

180d

cm_local_influx_msmlevel3retentionpolicyduration

rp_msm_deferred

cm_local_influx_msmdeferredretentionpolicyduration

rp_ppmp_meta_data

30d

cm_local_influx_eventretentionpolicyduration

In order to update the retention policy duration for the given retention use the following query with the Influx DB

ALTER RETENTION POLICY {RetentionName} ON {DatabaseName} DURATION {RetentionDuration}

For more information check out the Influx Documentation at https://archive.docs.influxdata.com/influxdb/v0.9/query_language/database_management/#modify-retention-policies-with-alter-retention-policy

How-To: Configure InfluxDB Access for on Prem BD Environments

This guide outlines the process for obtaining and configuring InfluxDB credentials for your K3s and Radium environments, leveraging the existing BCI/OPS2 managed Influx On-Prem Cluster.

Step 1: Request InfluxDB Credentials from BCI/OPS2

To access the InfluxDB cluster, you first need to request appropriate credentials from the BCI/OPS2 team.

Compose an Email to BCI/OPS2

Use the following address: operationsteam.nexeedias@de.bosch.com

Subject Line

Clearly state the purpose of your request. A recommended format is:

InfluxDB User Request: [Your Environment Name] - CM and PQM

Example

InfluxDB User Request: PREP16 - CM and PQM

Email Body

Clearly specify the environment for which you require credentials and the user types needed:

CM - Configuration Management
PQM - Performance Quality Management

Adhere to the specified user naming convention: ias_<environmentName>_cm and ias_<environmentName>_pqm.

Example Email Content

Dear BCI/OPS2 Team,

We need a new Influx user/db on Influx on prem Enterprise Cluster for CM and PQM for prep16 Environment.

cm_user: ias_prep16_cm
pqm_user: ias_prep16_pqm

Thanks,
[Your Name]

Send the email. BCI/OPS2 will then create the requested users according to their internal procedures and provide you with the necessary credentials.

Step 2: Add InfluxDB Credentials to custom-values.yml

Once you receive the InfluxDB credentials (username, password, API token if applicable, and potentially database name/retention policy details) from BCI/OPS2, you need to integrate them into your environment’s custom-values.yml file.

global:
 serverInstances:
  externalinflux:
    host: ppm-influxdb-dev-01.de.bosch.com
    port: 6665
    tls: true
    type: INFLUXDB
    default: false
 modules:
  cm:
    enabled: true
    databases:
     influxcm:
        userName: ias_prep16_cm
        name: ias_prep16_cm
        password: <pwd>
        serverInstance: externalinflux

For production environments, it is highly recommended to store these sensitive credentials in Vault and reference those secrets in your custom-values.yml rather than hardcoding them directly.

Step 3: Deploy/Update Your Environment

With the custom-values.yml updated, proceed with deploying or updating your K3s/Radium environment. The deployment process will now pick up the new InfluxDB credentials, allowing your applications to connect to the BCI/OPS2 managed InfluxDB cluster.