ELMA365

https://elma365.com/ru/help/
Admin
ELMA365 is a Low-code platform for business process management (BPM), CRM, document management, and...
Tokens:3,893,030
Snippets:15,384
Trust Score:10
Update:3 weeks ago
Show doc for...
Tokens:
Raw
### RelativeDatetime() examples for start period

Source: https://elma365.com/ru/help/platform/eql-syntax.html

Examples of start parameter values: 0h, +1m, -1w+1d. These define the beginning of the period.

```text
0h
```

```text
+1m
```

```text
-1w+1d
```

--------------------------------

### Enable containerd and kubelet services

Source: https://elma365.com/ru/help/platform/kubernetes-on-redos.html

Starts containerd and adds it to startup, then enables kubelet.service. Run as root on all nodes.

```bash
systemctl enable --now containerd
```

```bash
systemctl enable kubelet.service
```

--------------------------------

### Get installed values-elma365.yaml

Source: https://elma365.com/ru/help/platform/change-settings-enterprise.html

Reads the parameters file used during the ELMA365 installation. Optionally specify a namespace with -n.

```bash
helm [-n namespace] list  
helm [-n namespace] get values elma365 > values-elma365-installed.yaml
```

--------------------------------

### resources example

Source: https://elma365.com/ru/help/business_solutions/configmap.html

Пример настройки ресурсов микросервиса: requests указывают выделяемые память и CPU, limits — максимальные значения. Значения из официальной документации Kubernetes.

```yaml
resources:  
requests:  
memory: "512Mi"  
cpu: "500m"  
limits:  
memory: "2048Mi"  
cpu: "1000m"
```

--------------------------------

### Create and configure /etc/patroni/config.yml

Source: https://elma365.com/ru/help/configure-postgresql.html

Create the Patroni configuration file /etc/patroni/config.yml and populate it with the initial configuration example. Replace IP addresses with your own on each cluster node; note the comments in the file.

```bash
sudo nano /etc/patroni/config.yml
```

```yaml
scope: postgres-cluster # одинаковое значение на всех узлах  
name: postgresql-server1 # разное значение на всех узлах  
namespace: /service/ # одинаковое значение на всех узлах  
  
restapi:  
listen: postgres-server1.your_domain:8008 # адрес узла, на котором находится этот файл  
connect_address: postgres-server1.your_domain:8008 # адрес узла, на котором находится этот файл  
  
etcd:  
hosts: postgres-server1.your_domain:2379,postgres-server2.your_domain:2379,postgres-server3.your_domain:2379 # список всех узлов, на которых установлен etcd  
  
bootstrap:  
method: initdb  
dcs:  
ttl: 30  
loop_wait: 10  
retry_timeout: 10  
maximum_lag_on_failover: 1048576  
master_start_timeout: 300  
synchronous_mode: **false**  
synchronous_mode_strict: **false**  
synchronous_node_count: 1  
postgresql:  
use_pg_rewind: **true**  
use_slots: **true**  
parameters:  
max_connections: 2000  
superuser_reserved_connections: 5  
max_locks_per_transaction: 64  
max_prepared_transactions: 0  
huge_pages: **try**  
shared_buffers: 512MB  
work_mem: 128MB  
maintenance_work_mem: 256MB  
effective_cache_size: 4GB  
checkpoint_timeout: 15min  
checkpoint_completion_target: 0.9  
wal_compression: on  
min_wal_size: 2GB  
max_wal_size: 4GB  
wal_buffers: 32MB  
default_statistics_target: 1000  
seq_page_cost: 1  
random_page_cost: 4  
effective_io_concurrency: 2  
synchronous_commit: on  
autovacuum: on  
autovacuum_max_workers: 5  
autovacuum_vacuum_scale_factor: 0.1  
autovacuum_analyze_scale_factor: 0.05  
autovacuum_vacuum_cost_limit: 200  
autovacuum_vacuum_cost_delay: 20  
autovacuum_naptime: 15s  
max_files_per_process: 4096  
archive_mode: on  
archive_timeout: 1800s  
archive_command: cd .  
wal_level: replica  
wal_keep_segments: 130  
max_wal_senders: 10  
max_replication_slots: 10  
hot_standby: on  
hot_standby_feedback: True  
wal_log_hints: on  
shared_preload_libraries: pg_stat_statements,auto_explain  
pg_stat_statements.max: 10000  
pg_stat_statements.track: all  
pg_stat_statements.save: off  
auto_explain.log_min_duration: 10s  
auto_explain.log_analyze: **true**  
auto_explain.log_buffers: **true**  
auto_explain.log_timing: **false**  
auto_explain.log_triggers: **true**  
auto_explain.log_verbose: **true**  
auto_explain.log_nested_statements: **true**  
standard_conforming_strings: true  
track_io_timing: on  
log_lock_waits: on  
log_temp_files: 3  
track_activities: on  
track_counts: on  
track_functions: all  
log_checkpoints: on  
logging_collector: on  
log_truncate_on_rotation: on  
log_rotation_age: 1d  
log_rotation_size: 0  
log_line_prefix: '%t [%p-%l] %r %q%u@%d '  
log_filename: 'postgresql-%a.log'  
log_directory: /**var** /log/postgresql  
  
initdb: # List options to be passed on to initdb  
- encoding: UTF8  
- locale: en_US.UTF-8  
- data-checksums  
  
pg_hba: # должен содержать адреса ВСЕХ машин, используемых в кластере  
- local all postgres peer  
- local all all peer  
- host all all 0.0.0.0/0 md5  
- host replication replicator localhost trust  
- host replication replicator 192.168.1.1/32 md5  
- host replication replicator 192.168.1.2/32 md5  
- host replication replicator 192.168.1.3/32 md5  
  
postgresql:  
listen: 192.168.1.1,127.0.0.1:5432 # адрес узла, на котором находится этот файл  
connect_address: 192.168.1.1:5432 # адрес узла, на котором находится этот файл  
use_unix_socket: **true**  
data_dir: /**var** /lib/postgresql/13/main # каталог данных  
bin_dir: /usr/lib/postgresql/13/bin  
config_dir: /etc/postgresql/13/main  
pgpass: /**var** /lib/postgresql/.pgpass_patroni  
authentication:  
replication:  
username: replicator  
password: ReplicatorPassword  
superuser:  
username: postgres  
password: PostgresPassword  
parameters:  
unix_socket_directories: /**var** /run/postgresql  
pg_hba: # должен содержать адреса ВСЕХ машин, используемых в кластере  
- local all postgres peer  
- local all all peer  
- host all all 0.0.0.0/0 md5  
- host replication replicator localhost trust  
- host replication replicator 192.168.1.1/32 md5  
- host replication replicator 192.168.1.2/32 md5  
- host replication replicator 192.168.1.3/32 md5  
  
remove_data_directory_on_rewind_failure: **false**  
remove_data_directory_on_diverged_timelines: **false**  
****  
create_replica_methods:  
- basebackup  
basebackup:  
max-rate: '100M'  
checkpoint: 'fast'
```

--------------------------------

### values-envoy-gateway.yaml - Envoy Gateway Configuration

Source: https://elma365.com/ru/help/platform/envoy-gateway.html

Example configuration for Envoy Gateway installation, including gateway-helm deployment settings and envoyGateway controller configuration. Used in Step 2 of the installation process.

```yaml
## Настройки envoy-gateway  
gateway-helm:  
deployment:  
envoyGateway:  
resources:  
limits:  
memory: 1024Mi  
requests:  
cpu: 100m  
memory: 256Mi  
## Настройки конфигурации  
config:  
envoyGateway:  
gateway:  
controllerName: gateway.envoyproxy.io/gatewayclass-controller  
provider:  
type: Kubernetes  
---
```

--------------------------------

### destroy() example: clear interval on page close

Source: https://elma365.com/ru/help/crm/widget_functions.html

Stops an automatic refresh interval when the widget is destroyed. The example includes onInit() to start the interval, a setIntervalRefresh() function, and destroy() to clear the interval, preventing server errors from overlapping timers.

```typescript
async function onInit(): Promise<void> {  
// await refresh();  
setIntervalRefresh();  
}  
  
let intervalID: number;  
  
declare const window: {  
setInterval: (fn: () => void, interval: number) => number;  
clearInterval: (clearInterval: number) => void;  
};  
  
async function setIntervalRefresh () {  
intervalID = window.setInterval(() => {  
refresh();  
}, 3000);  
}  
  
async function destroy(): Promise<void> {  
window.clearInterval(intervalID);  
}
```
Tokens:
Raw