5 Configuration API Specifications
Note:
All the configuration updates are polled every 5 second from the databases, it takes 5 to 10 seconds to refresh the configuration in the application.5.1 Configuration APIs for UDR Microservices
This section describes the configuration APIs for UDR microservices.
Table 5-1 Configuration APIs for UDR microservices
| HTTP Method | Sample REST Request URL | Sample Response | Possible Error Codes |
|---|---|---|---|
| GET | http://ocudr-nudr-config.myudr:5001/nudr-config/v1/udr.nudrservice.cfg/DR-SERVICE |
Result Code: 200 OK Payload
|
NA |
| GET | http://ocudr-nudr-config.myudr:5001/nudr-config/v1/udr.notifyservice.cfg/NOTIFY-SERVICE |
Result Code: 200 OK Payload
|
NA |
| GET | http://ocudr-nudr-config.myudr:5001/nudr-config/v1/udr.global.cfg/GLOBAL |
Result Code: 200 OK Payload
|
NA |
| GET | http://ocudr-nudr-config.myudr:5001/nudr-config/v1/udr.diamgateway.cfg/DIAMETER-GATEWAY |
Result Code: 200 OK Payload
|
NA |
| GET | http://ocudr-nudr-config.myudr:5001/nudr-config/v1/udr.biservice.cfg/BULK_IMPORT |
Result Code: 200 OK Payload
|
NA |
| GET | http://localhost:8081/nudr-config/v1/udr.diamgateway.congestion.cfg/DGW-CONGESTION |
Result Code: 200 OK Payload
|
NA |
| GET | http://ocudr-nudr-config.myudr:5001/nudr-config/v1/udr.nudrprovservice.cfg/DR-PROV-SERVICE |
Result Code: 200 OK Payload
|
NA |
| GET | http://ocudr-nudr-config.myudr:5001/nudr-config/v1/udr.bulkimportservice.cfg/BULK_IMPORT_CFG |
Result Code: 200 OK Payload
|
NA |
| GET | http://ocudr-nudr-config.myudr:5001/nudr-config/v1/udr.exporttool.cfg/EXPORT_TOOL_CFG |
Result Code: 200 OK Payload
|
NA |
| GET | http://ocudr-nudr-config.myudr:5001/udr/nf-common-component/v1/operationalState |
Result Code: 200 OK Payload
|
|
| GET | http://ocudr-nudr-config.myudr:5001/udr/nf-common-component/v1/operationalStateHistoryIf offset is set to any value greater than 0 then it will return an empty array Value of the limit
greater than 5 displays only 5 records with query
params: |
Result Code: 200 OK Payload
|
|
| GET | http://ocudr-nudr-config.myudr:5001/nudr-config/v1/udr.exporttoolfilestatus.cfg/EXPORT_TOOL_FILE_STATUS |
Result Code: 200 OK Payload
|
|
| GET | http://ocudr-nudr-config.myudr:5001/nudr-config/v1/udr.exporttoolstatus.cfg/EXPORT_TOOL_STATUS |
Result Code: 200 OK Payload
|
|
| GET | http://ocudr-nudr-config.myudr:5001/nudr-config/v1/udr.exporttoolstatus.cfg/EXPORT_TOOL_STATUS/export-2023-01-16T14:12:33 |
Result Code: 200 OK Payload
|
|
| PUT |
Payload
|
Result Code: 200 OK |
|
| PUT | http://ocudr-nudr-config.myudr:5001/nudr-config/v1/udr.bulkimportservice.cfg/BULK_IMPORT_CFGPayload |
Result Code: 200 OK |
|
| PUT | http://ocudr-nudr-config.myudr:5001/nudr-config/v1/udr.exporttool.cfg/EXPORT_TOOL_CFGPayload |
Result Code: 200 OK |
|
| PUT |
Payload
|
Result Code: 200 OK |
|
| PUT |
payload |
Result Code: 200 OK |
Result Code: 200 OK |
| PUT |
payload
|
Result Code: 200 OK |
|
| PUT |
payload
|
200 OK Note: Do not change the default value of
|
|
| PUT | http://ocudr-nudr-config.myudr:5001/nudr-config/v1/udr.nudrprovservice.cfg/DR-PROV-SERVICEPayload |
Result Code: 200 OK |
|
| PUT | http://ocudr-nudr-config.myudr:5001/nudr-config/v1/udr.bulkimportservice.cfg/BULK_IMPORT_CFGPayload |
Result Code: 200 OK |
|
| PUT | http://ocudr-nudr-config.myudr:5001/udr/nf-common-component/v1/operationalStatePayload |
Result Code: 200 OK |
|
| DELETE |
http://ocudr-nudr-config.myudr:5001/nudr-config/v1/udr.exporttoolstatus.cfg/EXPORT_TOOL_STATUS/export-2023-01-16T14:12:33 |
Result Code: 200 OK |
|
5.2 Configuration APIs for Common Services
This section describes the configuration APIs for common services.
Table 5-2 Common Services Configuration APIs
| HTTP Method | Sample Request REST URL | Sample Response |
|---|---|---|
| PUT | http://localhost:8081/udr/nf-common-component/v1/nrf-client-nfmanagement/nfProfileListRequest |
200 OK |
| GET | http://localhost:8081/udr/nf-common-component/v1/nrf-client-nfmanagement/nfProfileList |
200 OK
|
| GET | http://<nudr-config-host>:<nudr-config-port>/udr/nf-common-component/v1/app-info/nfScoring |
200 OK
|
| PUT | http://<nudr-config-host>:<nudr-config-port>/udr/nf-common-component/v1/app-info/nfScoring |
200 OK |
| GET | http://<nudr-config-host>:<nudr-config-port>/udr/nf-common-component/v1/nfscore |
200 OK
|
| GET | http://<nudr-config-host>:<nudr-config-port>/udr/nf-common-component/v1/igw-sig/podProtectionByRateLimiting |
200 OK
|
| PUT | http://<nudr-config-host>:<nudr-config-port>/udr/nf-common-component/v1/igw-sig/podProtectionByRateLimiting |
200 OK |
| GET | http://<nudr-config-host>:<nudr-config-port>/udr/nf-common-component/v1/igw-sig/congestionConfig |
200 OK
|
| PUT | http://<nudr-config-host>:<nudr-config-port>/udr/nf-common-component/v1/igw-sig/congestionConfig |
200 OK |
5.2.1 Ingress Gateway Signaling APIs
This section describes the configuration APIs for Ingress Gateway Signaling.
Table 5-3 Ingress Gateway Signalling APIs for common services
| Method | Request | Response | Notes |
|---|---|---|---|
|
PUT |
Request body: |
200 OK Response body: |
Possible error codes 400Bad Request : Duplicate keys in array |
|
PATCH |
Request body: |
200 OK |
Possible error codes 400Bad Request : Duplicate keys in array |
|
GET |
|
200 OK Response body: |
NA |
|
PUT |
Request body: |
200 OK Response body: |
Possible error codes 400Bad Request : Could not Validate Json |
|
PATCH |
Request body: |
200 OK |
Possible error codes 400 Bad Request: |
|
GET |
|
200 OK Response body: |
NA |
|
PUT |
Request body: |
200 OK |
Possible error codes 400 Bad Request: Could not Validate Json |
|
PATCH |
Request body: |
200 OK |
Possible error codes 400 Bad Request: Could not Validate Json |
|
GET |
|
200 OK Response body: |
NA |
|
PUT |
Request body: |
200 OK |
Possible error codes 400 Bad Request: Could not Validate Json |
|
PATCH |
Request body: |
200 OK |
Possible error codes 400 Bad Request: Could not Validate Json |
|
PUT |
Request body: |
200 OK |
Possible error codes 400 Bad Request: Could not Validate Json |
|
PATCH |
Request body: |
200 OK |
Possible error codes 400 Bad Request: Could not Validate Json |
|
GET |
|
200 OK Response body: |
NA |
|
PUT |
Request body: |
200 OK |
Possible error codes 400 Bad Request: Could not Validate Json |
|
PATCH |
Request body: |
200 OK |
Possible error codes 400 Bad Request: Could not Validate Json |
|
GET |
|
200 OK Response body: |
NA |
|
PUT |
Request body: |
200 OK |
Possible error codes 400 Bad Request: Could not Validate Json |
|
PATCH |
Request body: |
200 OK |
Possible error codes 400 Bad Request: Could not Validate Json |
|
GET |
|
200 OK Response body: |
NA |
|
PUT |
Request body: Additional request body: |
200 OK |
NA |
|
GET |
|
200 OK Response body: |
NA |
|
PATCH |
Request body: |
200 OK |
NA |
|
GET |
|
Response body: |
NA |
|
PUT |
Request body: |
NA | NA |
|
GET |
|
200 OK Response body: |
NA |
|
PUT |
Request body: |
200 OK |
NA |
5.2.2 Ingress Gateway Provisioning APIs
This section describes the configuration APIs for Ingress Gateway Provisioning.
Table 5-4 Ingress Gateway Provisioning APIs for common services
| Method | Request | Response | Notes |
|---|---|---|---|
|
PUT |
Request body: |
200 OK |
Possible error codes: 400 Bad Request: Could not Validate Json |
|
PATCH |
Request body: |
200 OK |
Possible error codes: 400 Bad Request: Could not Validate Json |
|
GET |
|
200 OK Response body: |
NA |
|
PUT |
Request body (enable): Request body (disable): |
200 OK |
NA |
|
GET |
|
200 OK Response body: |
NA |
|
PATCH |
Request body: |
200 OK |
NA |
5.2.3 Enable cnDBTier Metrics with OSO Prometheus
kubectl create -f <.yaml> -n <nsdbtier>apiVersion: networking.istio.io/v1alpha3
kind: ServiceEntry
metadata:
name: cndb-to-mysql-external-se
spec:
exportTo:
- "."
hosts:
- mysql-connectivity-service
location: MESH_EXTERNAL
ports:
- number: 3306
name: mysql2
protocol: MySQL
---
apiVersion: networking.istio.io/v1alpha3
kind: ServiceEntry
metadata:
name: nf-to-nf
spec:
exportTo:
- "."
hosts:
- "*.$DOMAIN_NAME" # DOMAIN_NAME must be replaced with the deployed CNE Domain name
location: MESH_EXTERNAL
ports:
- number: 80
name: HTTP2-80
protocol: TCP
- number: 8080
name: HTTP2-8080
protocol: TCP
- number: 3306
name: TCP-3306
protocol: TCP
- number: 1186
name: TCP-1186
protocol: TCP
- number: 2202
name: TCP-2202
protocol: TCP
resolution: NONE
---
apiVersion: security.istio.io/v1beta1
kind: PeerAuthentication
metadata:
name: default
spec:
mtls:
mode: PERMISSIVE
---
apiVersion: networking.istio.io/v1alpha3
kind: ServiceEntry
metadata:
name: nf-to-kube-api-server
spec:
hosts:
- kubernetes.default.svc.$DOMAIN_NAME # DOMAIN_NAME must be replaced with the deployed CNE Domain name
exportTo:
- "."
addresses:
- 172.16.13.4
location: MESH_INTERNAL
ports:
- number: 443
name: https
protocol: HTTPS
- number: 6443
name: https-1
protocol: HTTPS
resolution: NONE
---
##################################################################################
# #
# Copyright (c) 2022 Oracle and/or its affiliates. All rights reserved. #
# #
##################################################################################
nameOverride: prom
## Helm-Test (Optional)
# Values needed for helm-test, Comment the entire Section if Helm-test not needed.
helmtestimage: occne-repo-host:5000/k8s.gcr.io/ingress-nginx/controller:v1.3.1
useasm: false
namespace: ocudr-ns
clustername: cne-23-1-rc2
resources:
limits:
cpu: 10m
memory: 32Mi
requests:
cpu: 10m
memory: 32Mi
promsvcname: oso-prom-svr
almsvcname: oso-prom-alm
prometheushealthyurl: /prometheus/-/healthy
prometheusreadyurl: /prometheus/-/ready
# Note: There are 3 types of label definitons provided in this custom values file
# TYPE1: Global(allResources)
# TYPE2: lb & nonlb TYPE label only
# TYPE3: service specific label
## NOTE: POD level labels can be inserted using the specific pod label sections, every pod/container has this label defined below in all components sections.
# ******** Custom Extension Global Parameters ********
#**************************************************************************
global_oso:
# Prefix & Suffix that will be added to containers
k8Resource:
container:
prefix:
suffix:
# Service account for Prometheus, Alertmanagers
serviceAccountNamePromSvr: ""
serviceAccountNameAlertMgr: ""
customExtension:
# TYPE1 Label
allResources:
labels: {}
# TYPE2 Labels
lbServices:
labels: {}
nonlbServices:
labels: {}
lbDeployments:
labels: {}
nonlbDeployments:
labels: {}
lbStatefulSets:
labels: {}
# Add annotations for disabling sidecar injections into oso pods here
# eg: annotations:
# - sidecar.istio.io/inject: "false"
annotations:
- sidecar.istio.io/inject: "false"
## Setting this parameter to false will disable creation of all default clusterrole, clusterolebing, role, rolebindings for the componenets that are packaged in this csar.
rbac:
create: true
podSecurityPolicy:
enabled: false
## Define serviceAccount names for components. Defaults to component's fully qualified name.
##
serviceAccounts:
alertmanager:
create: true
name:
annotations: {}
nodeExporter:
create: false
name:
annotations: {}
pushgateway:
create: false
name:
annotations: {}
server:
create: true
name:
annotations: {}
alertmanager:
enabled: true
## Use a ClusterRole (and ClusterRoleBinding)
## - If set to false - Define a Role and RoleBinding in the defined namespaces ONLY
## This makes alertmanager work - for users who do not have ClusterAdmin privs, but wants alertmanager to operate on their own namespaces, instead of clusterwide.
useClusterRole: false
## Set to a rolename to use existing role - skipping role creating - but still doing serviceaccount and rolebinding to the rolename set here.
useExistingRole: false
## alertmanager resources name
name: alm
image:
repository: occne-repo-host:5000/quay.io/prometheus/alertmanager
tag: v0.24.0
pullPolicy: IfNotPresent
extraArgs:
data.retention: 120h
prefixURL: /cne-23-1-rc2/alertmanager
baseURL: "http://localhost/cne-23-1-rc2/alertmanager"
configFileName: alertmanager.yml
nodeSelector: {}
affinity: {}
podDisruptionBudget:
enabled: true
minAvailable: 1
persistentVolume:
enabled: true
accessModes:
- ReadWriteOnce
annotations: {}
## alertmanager data Persistent Volume existing claim name
## Requires alertmanager.persistentVolume.enabled: true
## If defined, PVC must be created manually before volume will be bound
existingClaim: ""
mountPath: /data
size: 2Gi
storageClass: "standard"
## Annotations to be added to alertmanager pods
##
podAnnotations: {}
## Labels to be added to Prometheus AlertManager pods
##
podLabels: {}
replicaCount: 2
## Annotations to be added to deployment
##
deploymentAnnotations: {}
statefulSet:
## If true, use a statefulset instead of a deployment for pod management.
## This allows to scale replicas to more than 1 pod
##
enabled: true
annotations: {}
labels: {}
podManagementPolicy: OrderedReady
## Alertmanager headless service to use for the statefulset
##
headless:
annotations: {}
labels: {}
## Enabling peer mesh service end points for enabling the HA alert manager
## Ref: https://github.com/prometheus/alertmanager/blob/master/README.md
enableMeshPeer: true
servicePort: 80
## alertmanager resource requests and limits
## Ref: http://kubernetes.io/docs/user-guide/compute-resources/
##
resources:
limits:
cpu: 20m
memory: 64Mi
requests:
cpu: 20m
memory: 64Mi
service:
annotations: {}
labels: {}
clusterIP: ""
loadBalancerIP: ""
loadBalancerSourceRanges: []
servicePort: 80
# nodePort: 30000
sessionAffinity: None
type: ClusterIP
## Monitors ConfigMap changes and POSTs to a URL
## Ref: https://github.com/jimmidyson/configmap-reload
##
configmapReload:
prometheus:
enabled: true
## configmap-reload container name
##
name: configmap-reload
image:
repository: occne-repo-host:5000/docker.io/jimmidyson/configmap-reload
tag: v0.8.0
pullPolicy: IfNotPresent
# containerPort: 9533
## Additional configmap-reload mounts
##
extraConfigmapMounts: []
## Security context to be added to configmap-reload container
containerSecurityContext: {}
## configmap-reload resource requests and limits
## Ref: http://kubernetes.io/docs/user-guide/compute-resources/
##
resources:
limits:
cpu: 10m
memory: 32Mi
requests:
cpu: 10m
memory: 32Mi
alertmanager:
enabled: true
name: configmap-reload
image:
repository: occne-repo-host:5000/docker.io/jimmidyson/configmap-reload
tag: v0.8.0
pullPolicy: IfNotPresent
# containerPort: 9533
## Additional configmap-reload mounts
##
extraConfigmapMounts: []
# - name: prometheus-alerts
# mountPath: /etc/alerts.d
# subPath: ""
# configMap: prometheus-alerts
# readOnly: true
resources:
limits:
cpu: 10m
memory: 32Mi
requests:
cpu: 10m
memory: 32Mi
kubeStateMetrics:
enabled: false
nodeExporter:
enabled: false
server:
enabled: true
## namespaces to monitor (instead of monitoring all - clusterwide). Needed if you want to run without Cluster-admin privileges.
namespaces: []
# - ocudr-ns
name: svr
image:
repository: occne-repo-host:5000/quay.io/prometheus/prometheus
tag: v2.39.1
pullPolicy: IfNotPresent
prefixURL: /cne-23-1-rc2/prometheus
baseURL: "http://localhost/cne-23-1-rc2/prometheus"
## Additional server container environment variables
env: []
# List of flags to override default parameters, e.g:
# - --enable-feature=agent
# - --storage.agent.retention.max-time=30m
defaultFlagsOverride: []
extraFlags:
- web.enable-lifecycle
## web.enable-admin-api flag controls access to the administrative HTTP API which includes functionality such as
## deleting time series. This is disabled by default.
# - web.enable-admin-api
##
## storage.tsdb.no-lockfile flag controls BD locking
# - storage.tsdb.no-lockfile
##
## storage.tsdb.wal-compression flag enables compression of the write-ahead log (WAL)
# - storage.tsdb.wal-compression
## Path to a configuration file on prometheus server container FS
configPath: /etc/config/prometheus.yml
global:
scrape_interval: 1m
scrape_timeout: 30s
evaluation_interval: 1m
#remoteWrite:
#- url OSO_CORTEX_URL
# remote_timout (default = 30s)
#remote_timeout: OSO_REMOTE_WRITE_TIMEOUT
# bearer_token for cortex server to be configured
# bearer_token: BEARER_TOKEN
extraArgs:
storage.tsdb.retention.size: 1GB
## Additional Prometheus server Volume mounts
##
extraVolumeMounts: []
## Additional Prometheus server Volumes
##
extraVolumes: []
## Additional Prometheus server hostPath mounts
##
extraHostPathMounts: []
# - name: certs-dir
# mountPath: /etc/kubernetes/certs
# subPath: ""
# hostPath: /etc/kubernetes/certs
# readOnly: true
extraConfigmapMounts: []
nodeSelector: {}
affinity: {}
podDisruptionBudget:
enabled: false
maxUnavailable: 1
persistentVolume:
enabled: true
accessModes:
- ReadWriteOnce
annotations: {}
## Prometheus server data Persistent Volume existing claim name
## Requires server.persistentVolume.enabled: true
## If defined, PVC must be created manually before volume will be bound
existingClaim: ""
size: 2Gi
storageClass: "standard"
## Annotations to be added to Prometheus server pods
##
podAnnotations: {}
## Labels to be added to Prometheus server pods
##
podLabels: {}
## Prometheus AlertManager configuration
##
alertmanagers:
- kubernetes_sd_configs:
- role: pod
# Namespace to be configured
namespaces:
names:
- ocudr-ns
- dbtier-ns
path_prefix: cne-23-1-rc2/alertmanager
relabel_configs:
- source_labels: [__meta_kubernetes_namespace]
# namespace to be configured
regex: ocudr-ns
action: keep
- source_labels: [__meta_kubernetes_pod_label_app]
regex: prom
action: keep
- source_labels: [__meta_kubernetes_pod_label_component]
regex: alm
action: keep
- source_labels: [__meta_kubernetes_pod_annotation_prometheus_io_probe]
regex: .*
action: keep
- source_labels: [__meta_kubernetes_pod_container_port_number]
regex:
action: drop
## Use a StatefulSet if replicaCount needs to be greater than 1 (see below)
##
replicaCount: 1
## Annotations to be added to deployment
##
deploymentAnnotations: {}
statefulSet:
## If true, use a statefulset instead of a deployment for pod management.
## This allows to scale replicas to more than 1 pod
##
enabled: false
annotations: {}
labels: {}
podManagementPolicy: OrderedReady
resources:
limits:
cpu: 2
memory: 4Gi
requests:
cpu: 2
memory: 4Gi
service:
enabled: true
annotations: {}
labels: {}
clusterIP: ""
externalIPs: []
loadBalancerIP: ""
loadBalancerSourceRanges: []
servicePort: 80
sessionAffinity: None
type: NodePort
## If using a statefulSet (statefulSet.enabled=true), configure the
## service to connect to a specific replica to have a consistent view
## of the data.
statefulsetReplica:
enabled: false
replica: 0
retention: "7d"
pushgateway:
## If false, pushgateway will not be installed
##
enabled: false
## alertmanager ConfigMap entries
##
alertmanagerFiles:
alertmanager.yml:
global: {}
# slack_api_url: ''
receivers:
- name: default-receiver
# slack_configs:
# - channel: '@you'
# send_resolved: true
route:
group_wait: 10s
group_interval: 5m
receiver: default-receiver
repeat_interval: 3h
## Prometheus server ConfigMap entries for rule files (allow prometheus labels interpolation)
ruleFiles: {}
## Prometheus server ConfigMap entries
##
serverFiles:
## Alerts configuration
## Ref: https://prometheus.io/docs/prometheus/latest/configuration/alerting_rules/
alerting_rules.yml: {}
## DEPRECATED DEFAULT VALUE, unless explicitly naming your files, please use alerting_rules.yml
alerts: {}
## Records configuration
## Ref: https://prometheus.io/docs/prometheus/latest/configuration/recording_rules/
recording_rules.yml: {}
## DEPRECATED DEFAULT VALUE, unless explicitly naming your files, please use recording_rules.yml
rules: {}
prometheus.yml:
rule_files:
- /etc/config/recording_rules.yml
- /etc/config/alerting_rules.yml
## Below two files are DEPRECATED will be removed from this default values file
- /etc/config/rules
- /etc/config/alerts
scrape_configs:
- job_name: prometheus
metrics_path: cne-23-1-rc2/prometheus/metrics
static_configs:
- targets:
- localhost:9090
extraScrapeConfigs: |
- job_name: 'oracle-cnc-service'
kubernetes_sd_configs:
- role: service
namespaces:
names:
- ocudr-ns
- dbtier-ns
# - ns2
relabel_configs:
- source_labels: [__meta_kubernetes_service_annotation_oracle_com_cnc]
regex: true
action: keep
- source_labels: [__meta_kubernetes_service_annotation_prometheus_io_scrape]
action: keep
regex: true
- source_labels: [__meta_kubernetes_service_annotation_prometheus_io_path]
action: replace
target_label: __metrics_path__
regex: (.+)
- source_labels: [__address__, __meta_kubernetes_service_annotation_prometheus_io_port]
action: replace
regex: ([^:]+)(?::\d+)?;(\d+)
replacement: $1:$2
target_label: __address__
- action: labelmap
regex: __meta_kubernetes_service_label_(.+)
- source_labels: [__meta_kubernetes_namespace]
action: replace
target_label: kubernetes_namespace
- source_labels: [__meta_kubernetes_service_name]
action: replace
target_label: kubernetes_service_name
- job_name: 'oracle-cnc-pod'
kubernetes_sd_configs:
- role: pod
namespaces:
names:
- ocudr-ns
- dbtier-ns
# - ns2
relabel_configs:
- source_labels: [__meta_kubernetes_pod_annotation_oracle_com_cnc]
regex: true
action: keep
- source_labels: [__meta_kubernetes_pod_annotation_prometheus_io_scrape]
action: keep
regex: true
- source_labels: [__meta_kubernetes_pod_annotation_prometheus_io_path]
action: replace
target_label: __metrics_path__
regex: (.+)
- source_labels: [__address__, __meta_kubernetes_pod_annotation_prometheus_io_port]
action: replace
regex: ([^:]+)(?::\d+)?;(\d+)
replacement: $1:$2
target_label: __address__
- action: labelmap
regex: __meta_kubernetes_pod_label_(.+)
- source_labels: [__meta_kubernetes_namespace]
action: replace
target_label: kubernetes_namespace
- source_labels: [__meta_kubernetes_pod_name]
action: replace
target_label: kubernetes_pod_name
- job_name: 'oracle-cnc-endpoints'
kubernetes_sd_configs:
- role: endpoints
#namespaces:
# names:
# - ns1
# - ns2
relabel_configs:
- source_labels: [__meta_kubernetes_service_annotation_oracle_com_cnc]
regex: true
action: keep
- source_labels: [__meta_kubernetes_service_annotation_prometheus_io_scrape]
action: keep
regex: true
- source_labels: [__meta_kubernetes_service_annotation_prometheus_io_scheme]
action: replace
target_label: __scheme__
regex: (https?)
- source_labels: [__meta_kubernetes_service_annotation_prometheus_io_path]
action: replace
target_label: __metrics_path__
regex: (.+)
- source_labels: [__address__, __meta_kubernetes_service_annotation_prometheus_io_port]
action: replace
target_label: __address__
regex: ([^:]+)(?::\d+)?;(\d+)
replacement: $1:$2
- job_name: 'oracle-cnc-ingress'
kubernetes_sd_configs:
- role: ingress
#namespaces:
# names:
# - ns1
# - ns2
relabel_configs:
- source_labels: [__meta_kubernetes_ingress_annotation_oracle_com_cnc]
regex: true
action: keep5.2.4 Configuration APIs for Overload Handling
This section describes the configuration APIs on Ingress Gateway and perf-info microservices for overload handling.
Table 5-5 Configuration APIs on Ingress Gateway for Overload Handling
| HTTP Method | Sample Request REST URL | Sample Response |
|---|---|---|
| PUT |
igw-sig URL:
oc policy
mapping
igw-prov URL:
oc policy
mapping
|
Response is same as Request payload. |
| PATCH |
igw-sig URL: oc policy mapping
|
|
| GET |
igw-sig URL: oc policy mapping
|
|
| PUT |
igw-sig URL:
igw-prov URL:
For payload, see PUT - OC Discard Policy. |
Response is same as Request payload. |
| PATCH |
igw-sig URL: igw-prov URL: |
|
| PATCH |
igw-sig URL: igw-prov URL: |
|
| PUT |
igw-sig URL:
igw-prov URL:
For payload, see PUT - Error Code Profiles. |
Response is same as Request payload. |
| PATCH |
igw-sig URL: igw-prov URL: |
Response is same as Request payload. |
| GET |
igw-sig URL: igw-prov URL:
/udr/nf-common-component/v1/igw-prov/errorcodeprofiles |
|
| PUT |
igw-sig URL:
igw-prov URL:
For payload, see PUT - Routes Configuration. |
Response is same as Request payload. |
| PUT |
igw-sig URL:
igw-prov URL:
error code series
|
Response is same as Request payload. |
| PATCH |
igw-sig URL: igw-prov URL: error code series |
|
Table 5-6 Configuration APIs on perf-info for Overload Handling
| HTTP Method | Sample Request REST URL | Sample Response |
|---|---|---|
| PUT |
URL:
For payload, see PUT - Overload Threshold Configuration |
Response is same as Request payload. |
For more information about the Overload Handling configurable parameters, see Oracle Communications Cloud Native Core Unified Data Repository Installation and Upgrade Guide.
5.2.5 Configuration APIs for Rate Limit
This section describes the configuration APIs on Ingress Gateway for rate limiting feature.
Table 5-7 Configuration APIs on Ingress Gateway for Rate Limiting
| HTTP Method | Sample Request REST URL | Sample Response | Notes |
|---|---|---|---|
| PUT |
URL:
routesconfiguration
|
routesconfiguration
|
Response is same as request |
| PATCH |
URL: http://<nudr-config svc IP>:<port>/udr/nf-common-component/v1/igw-sig/routesconfiguration routesconfiguration |
routesconfiguration |
Possible error codes 400 Bad Request: Could not validate Json |
| GET |
URL: http://<nudr-config svc IP>:<port>/udr/nf-common-component/v1/igw-sig/routesconfiguration routesconfiguration
|
routesconfiguration |
- |
| PUT |
URL: http://<nudr-config-url:port>/udr/nf-common-component/v1/igw-sig/routelevelratelimiting routelevelratelimiting
|
routelevelratelimiting
|
Response is same as request |
| GET |
URL: http://<nudr-config-url:port>/udr/nf-common-component/v1/igw-sig/routelevelratelimiting routelevelratelimiting
|
routelevelratelimiting |
- |
| PUT |
URL:
errorcodeprofiles
|
errorcodeprofiles
|
Response is same as request |
Table 5-8 Pod Protection by Rate Limiting Configuration APIs
| HTTP Method | Sample Request REST URL | Sample Response |
|---|---|---|
| GET | http://<nudr-config-host>:<nudr-config-port>/udr/nf-common-component/v1/igw-sig/podProtectionByRateLimiting |
200 OK |
| PUT | http://<nudr-config-host>:<nudr-config-port>/udr/nf-common-component/v1/igw-sig/podProtectionByRateLimiting |
200 OK |
| GET | http://<nudr-config-host>:<nudr-config-port>/udr/nf-common-component/v1/igw-sig/congestionConfig |
200 OK |
| PUT | http://<nudr-config-host>:<nudr-config-port>/udr/nf-common-component/v1/igw-sig/congestionConfig |
200 OK |
5.2.5.1 Default Configuration Details for Rate Limit
The default configuration details for rate limit are:
Important:
The default deployment setup includes two Ingress Gateways and two DR pods. The following default rates are derived based on this deployment setup. If you want to scale up the pods, then adjust or configure the route rates accordingly. The route rates are available under routesconfiguration of http://10.75.229.75:31187/udr/nf-common-component/v1/igw/routesconfiguration.- RouteId-Path - traffic_mapping_http - nudr-dr
Table 5-9 Method wise Rate Details
Method Rate GET 200 PUT 300 POST 200 PATCH 200 DELETE 200 - RouteId-Path - traffic_mapping_http_prov - nudr-dr-prov
Table 5-10 Method wise Rate Details
Method Rate GET 200 PUT 300 POST 200 PATCH 200 DELETE 200 - RouteId-Path - traffic_mapping_http_group - nudr-group-id-map
Table 5-11 Method wise Rate Details
Method Rate GET 1350 - RouteId-Path - traffic_mapping_http_group_prov - nudr-group-id-map-prov
Table 5-12 Method wise Rate Details
Method Rate GET 800 PUT 200 DELETE 200 - RouteId-Path - traffic_mapping_http_slf_group_prov - slf-group-prov
Table 5-13 Method wise Rate Details
Method Rate GET 800 PUT 200 DELETE 200
5.3 Configuration APIs for Configurations Import and Export
Table 5-14 Configuration APIs for Configurations Import
| HTTP Method | Sample Request REST URL | Sample Response | Notes |
|---|---|---|---|
| POST | URL: http://10.75.229.157:31725/nudr-config/v1/import
|
Result Code: 201 Created Payload Import resource id: 552a4328-21ec-43aa-a460-58ce1df407ae |
This is the first step to initiate import. |
| GET | URL : http://10.75.229.157:31725/nudr-config/v1/import |
Result Code: 200 OK
Payload
|
This API is to get the existing import id.
404 Not Found 500 Internal Server Error |
| GET |
URL: Import resource id: 552a4328-21ec-43aa-a460-58ce1df407ae |
Result Code: 200 OK Payload |
This is the second step. Keep calling this API until "percentage": "100" |
| GET | URL: http://10.75.229.157:31725/nudr-config/v1/import/552a4328-21ec-43aa-a460-58ce1df407ae/reportImport resource id: 552a4328-21ec-43aa-a460-58ce1df407ae |
Result Code: 200 OK Payload |
This is the third step. This API gives complete import report. |
Table 5-15 Configuration APIs for Configurations Export
| HTTP Method | Sample Request REST URL | Sample Response | Notes |
|---|---|---|---|
| POST |
|
Result Code: 201 Created Payload Export resource id: 3e470fab-e131-4dbe-be67-ba7391729254 |
This is the first step to initiate export. |
| GET | To export all services : http://10.75.229.157:31725/nudr-config/v1/export |
Result Code: 200 OK
Payload
|
This API is to get the existing export id.
Possible error codes 404 Not Found 500 Internal Server Error |
| GET |
URI: Export resource id: 3e470fab-e131-4dbe-be67-ba7391729254 |
Result Code: 200 OK Payload |
This is the second step. Keep calling this API until "percentage": "100". |
| GET |
URI: Export resource id: 3e470fab-e131-4dbe-be67-ba7391729254 |
Result Code: 200 OK Payload |
This is the third step. This API gives complete export report. |
| GET |
URI: Export resource id: 3e470fab-e131-4dbe-be67-ba7391729254 |
Result Code: 200 OK exportedFiles_ 1.12.0_20210706080247.zip |
This is the fourth step. This API is used to download exported zip file. |
5.4 Configuration APIs for Loglevel
This section describes the configuration APIs for loglevel.
Table 5-16 Configuration APIs for Loglevel
| HTTP Method | Sample Request REST URL | Sample Response | Notes |
|---|---|---|---|
| GET | URI:
http://10.75.229.168:32310/nudr-config/v1/nudr-drservice/logging |
Result Code: 200 OK Payload
|
NA |
| GET | http://10.75.229.168:32310/nudr-config/v1/nudr-notify-service/logging |
Result Code: 200 OK Payload
|
NA |
| GET | http://10.75.229.168:32310/nudr-config/v1/nudr-diameterproxy/logging |
Result Code: 200 OK Payload
|
NA |
| GET | http://10.75.229.168:32310/nudr-config/v1/diam-gateway/logging |
Result Code: 200 OK Payload
|
NA |
| GET | http://10.75.229.168:32527/udr/nf-common-component/v1/igw-sig/logging |
Result Code: 200 OK Payload
|
NA |
| GET | http://10.75.229.168:32527/udr/nf-common-component/v1/igw-prov/logging |
Result Code: 200 OK Payload
|
NA |
| GET | http://10.75.229.168:32527/udr/nf-common-component/v1/egw/logging |
Result Code: 200 OK Payload
|
NA |
| GET | http://10.75.229.168:32527/udr/nf-common-component/v1/alt-route/logging |
Result Code: 200 OK Payload
|
NA |
| GET |
|
200 OK Response
|
|
| GET | http://10.75.229.168:31867/nudr-config/v1/all/logging |
Result Code: 200 OK Payload
|
NA |
| GET | http://10.75.229.168:32310/nudr-config/v1/nudr-dr-provservice/logging |
Result Code: 200
OK |
NA |
| GET |
http://10.75.229.168:32310/nudr-config/v1/nudr-bulk-import/logging |
Result Code: 200
OK |
NA |
| GET | http://10.75.229.168:32310/nudr-config/v1/nudr-export-tool/logging |
200 Created Payload
|
NA |
| GET | http://10.75.180.253:30601/nudr-config/v1/nudr-config/logging |
200 Created Payload
|
NA |
| PUT |
URI:
|
201 Created Payload
|
|
| PUT |
|
201 Created Payload
|
|
| PUT | http://10.75.229.168:32310/nudr-config/v1/nudr-diameterproxy/logging |
201 Created Payload
|
|
| PUT |
|
201 Created Payload
|
|
| PUT |
|
200 OK Payload
|
|
| PUT | http://10.75.229.168:32527/udr/nf-common-component/v1/igw-prov/logging |
200 OK Payload
|
|
| PUT |
|
200 OK Payload
|
|
| PUT |
|
200 OK Payload
|
|
| PUT |
|
200 OK Response
|
|
| PUT | http://10.75.229.168:32310/nudr-config/v1/nudr-dr-provservice/logging |
201 created Payload
|
|
| PUT |
http://10.75.229.168:32310/nudr-config/v1/nudr-bulk-import/logging |
201 created Payload
|
|
| PUT | http://10.75.229.168:32310/nudr-config/v1/nudr-export-tool/logging |
201 created Payload
|
|
| PUT | http://10.75.180.253:30601/nudr-config/v1/nudr-config/logging |
201 created Payload
|
|
5.5 Configuration APIs for Backend Pod Protection
Nudr-drservice
Table 5-17 Nudr-drservice
| Operation Type | Request | Response | Notes |
|---|---|---|---|
| GET | URI : http://<nudr-config-url>:<port>/nudr-config/v1/nudr-drservice/podProtectionByRateLimiting | Result Code: 200 OK
Payload:
|
404 NOT FOUND
400 BAD REQUEST |
| PUT | URI : http://<nudr-config-url>:<port>/nudr-config/v1/nudr-drservice/podProtectionByRateLimiting
Payload:
|
201 Created | 400 Bad Request: Schema validation failed |
| GET | URI : http://<nudr-config-url>:<port>/nudr-config/v1/nudr-drservice/congestionConfig | Result Code: 200 OK
Payload:
|
|
| PUT | URI : http://<nudr-config-url>:<port>/nudr-config/v1/nudr-drservice/congestionConfig
Payload:
|
201 Created | 400 Bad Request: Schema validation failed |
Nudr-prov-service
Table 5-18 Nudr-prov-service
| Operation Type | Request | Response | Notes |
|---|---|---|---|
| GET | URI : http://<nudr-config-url>:<port>/nudr-config/v1/nudr-dr-provservice/podProtectionByRateLimiting | Result Code: 200 OK
Payload:
|
404 NOT FOUND
400 BAD REQUEST |
| PUT | URI : http://<nudr-config-url>:<port>/nudr-config/v1/nudr-dr-provservice/podProtectionByRateLimiting
Payload:
|
201 Created | 404 NOT FOUND
400 BAD REQUEST |
| GET | URI : http://<nudr-config-url>:<port>/nudr-config/v1/nudr-dr-provservice/congestionConfig | Result Code: 200 OK
Payload:
|
404 NOT FOUND
400 BAD REQUEST |
| 404 NOT FOUND
400 BAD REQUEST |
URI : http://<nudr-config-url>:<port>/nudr-config/v1/nudr-dr-provservice/congestionConfig
Payload:
|
201 Created | 404 NOT FOUND
400 BAD REQUEST |
Notify-service
Table 5-19 Notify-service
| Operation Type | Request | Response | Notes |
|---|---|---|---|
| GET | http://<nudr-config-url>:<port>/nudr-config/v1/nudr-notify-service/podProtectionByRateLimiting | Result Code: 200OK
Payload:
|
404 NOT FOUND
400 BAD REQUEST |
| PUT | URL: http://10.75.229.168:32310/nudr-config/v1/nudr-notify-service/podProtectionByRateLimiting
Payload:
|
201 Created | 400 Bad Request: Schema validation failed |
| GET | URL: http://<nudr-config-url>:<port>/nudr-config/v1/nudr-notify-service/congestionConfig | Result Code: 200OK
Payload:
|
404 NOT FOUND
400 BAD REQUEST |
| PUT | URL: http://10.75.229.168:32310/nudr-config/v1/nudr-notify-service/congestionConfig
Payload:
|
201 Created | 400 Bad Request: Schema validation failed |
5.6 Common Configurations Global
Table 5-20 Configuration APIs for SBI Message Priority Header
| HTTP Method | Sample Request REST URL | Sample Response | Notes |
|---|---|---|---|
| GET | http://<nudr-config-svc>:<PORT>/udr/nf-common-component/v1/global-configuration/sbiserviceoperations | Result Code: 200 OK
SLF Payload
EIR Payload:
UDR Payload
|
NA |
| PUT | http://<nudr-config-svc>:<PORT>/udr/nf-common-component/v1/global-configuration/sbiserviceoperations | Result Code: 200 OK
SLF Payload
EIR Payload:
UDR Payload
|
Possible error codes 400 Bad Request : Could not validate Json |
| GET | http://<nudr-config-svc>:<PORT>/udr/nf-common-component/v1/global-configuration/sbimessagepriority | Result Code: 200 OK
Payload:
|
NA |
| PUT | http://<nudr-config-svc>:<PORT>/udr/nf-common-component/v1/global-configuration/sbimessagepriority | Result Code: 200 OK
Payload:
|
Possible error codes 400 Bad Request : Could not validate Json |
| GET | http://<nudr-config-svc>:<PORT>/udr/nf-common-component/v1/global-configuration/requestsmpheaders | Result Code: 200 OK
Payload:
|
NA |
| PUT | http://<nudr-config-svc>:<PORT>/udr/nf-common-component/v1/global-configuration/requestsmpheaders | Result Code: 200 OK
Payload:
|
Possible error codes 400 Bad Request : Could not validate Json |
| GET | http://<nudr-config-svc>:<PORT>/udr/nf-common-component/v1/global-configuration/prioritymappingrules | Result Code: 200 OK
Payload:
|
NA |
| PUT | http://<nudr-config-svc>:<PORT>/udr/nf-common-component/v1/global-configuration/prioritymappingrules | Result Code: 200 OK
Payload:
|
Possible error codes 400 Bad Request : Could not validate Json |
5.7 Configuration APIs for NRF Client
The following table describes the configuration APIs for NRF Client
Table 5-21 Configuration APIs for NRF Client
| Method | Request | Response | Notes |
|---|---|---|---|
|
PUT |
Request body:
|
200 OK |
Possible error codes: 400 Bad Request Could not Validate Json. 404 Not Found Configuration does not exist. Service, resource, or key not found. 500 Internal Server Error Internal error while reading or updating the common configuration. |
|
PATCH |
Request body:
|
200 OK |
Possible error codes: 400 Bad Request Could not Validate Json. 404 Not Found Configuration does not exist. Service, resource, or key not found. 500 Internal Server Error Internal error while reading or updating the common configuration. |
|
GET |
|
200 OK Response body:
|
Possible error codes: 404 Not Found Configuration does not exist. Service, resource, or key not found. 500 Internal Server Error Internal error while reading or updating the common configuration. |
|
PUT |
Request body:
|
200 OK |
Possible error codes: 400 Bad Request Could not Validate Json. 404 Not Found Configuration does not exist. Service, resource, or key not found. 500 Internal Server Error Internal error while reading or updating the common configuration. |
|
PATCH |
Request body:
|
200 OK |
Possible error codes: 400 Bad Request Could not Validate Json. 404 Not Found Configuration does not exist. Service, resource, or key not found. 500 Internal Server Error Internal error while reading or updating the common configuration. |
|
GET |
|
200 OK Response body:
|
Possible error codes: 404 Not Found Configuration does not exist. Service, resource, or key not found. 500 Internal Server Error Internal error while reading or updating the common configuration. |
|
PUT |
Request body:
|
200 OK |
Possible error codes: 400 Bad Request Could not Validate Json. 404 Not Found Configuration does not exist. Service, resource, or key not found. 500 Internal Server Error Internal error while reading or updating the common configuration. |
|
PATCH |
Request body:
|
200 OK |
Possible error codes: 400 Bad Request Could not Validate Json. 404 Not Found Configuration does not exist. Service, resource, or key not found. 500 Internal Server Error Internal error while reading or updating the common configuration. |
|
GET |
|
200 OK Response body:
|
Possible error codes: 404 Not Found Configuration does not exist. Service, resource, or key not found. 500 Internal Server Error Internal error while reading or updating the common configuration. |
|
PUT |
Request body:
|
200 OK |
Possible error codes: 400 Bad Request Could not Validate Json. 404 Not Found Configuration does not exist. Service, resource, or key not found. 500 Internal Server Error Internal error while reading or updating the common configuration. |
|
PATCH |
Request body:
|
200 OK |
Possible error codes: 400 Bad Request Could not Validate Json. 404 Not Found Configuration does not exist. Service, resource, or key not found. 500 Internal Server Error Internal error while reading or updating the common configuration. |
|
GET |
|
200 OK Response body:
|
Possible error codes: 404 Not Found Configuration does not exist. Service, resource, or key not found. 500 Internal Server Error Internal error while reading or updating the common configuration. |
5.8 List of Errors and their Details
The list of errors and their details are as follows:
Table 5-22 Error Code Catalogue
| Error Details | Possible Causes | Corrective Actions |
|---|---|---|
|
Error Code: E550 HTTP Response Code: 404 Category: CFG Error Description: The import or export ResourceId or report not found |
Provided import or export ResourceId is incorrect. The import or export report with the provided ResourceId is not found. |
Check if the provided import or export ResourceId is correct. |
|
Error Code: E551 HTTP Response Code: 500 Category: CFG Error Description: Retrieving the report or status of import or export when the operation is still in progress. |
Retrieving the report or status of import or export when the operation is still in progress. |
Try after the existing import or export is completed. |
|
Error Code: E552 HTTP Response Code: 500 Category: CFG Error Description:The import or exportt report is not generated. |
The import or export report creation failed. |
NA |
|
Error Code: E553 HTTP Response Code: 400 Category: CFG Error Description: Empty or incorrect MO passed. |
Empty MO value passed or the passed MO value is incorrect. |
Provide a valid MO value. |
|
Error Code: E554 HTTP Response Code: 400 Category: CFG Error Description: The file provided for the import has unsupported file format or file content. |
Import file other than ZIP file format is provided. Error reading zip stream or unable to extract contents of file. |
Check and upload the file with supported format and file content. |
| E555
HTTP Response Code: 500 Category: CFG Error Description: Another import or export operation request is in progress. |
Another import or export request is in progress. |
You must wait for previous requests to complete before performing another import or export operation. |
|
Error Code: E556 HTTP Response Code: 500 Category: CFG Error Description: Unable to download exported data |
Could not create exported JSON files. |
NA |
|
Error Code: E557 HTTP Response Code: 400 Category: CFG Error Description: Controlled Shutdown feature is disabled |
Controlled shutdown feature is disabled when updating OperationalStatus. |
Enable the controlled shutdown feature. |
|
Error Code: E558 HTTP Response Code: 400 Category: CFG Error Description: Invalid OperationalState |
Invalid OperationalState provided. |
Provide operationalState with "NORMAL" or "COMPLETE_SHUTDOWN" |
|
Error Code: E559 HTTP Response Code: 403 Category: CFG Error Description: Read only field can not be modified. |
Tried to modify a read only field. |
NA |
|
Error Code: E560 HTTP Response Code: 400 Category: CFG Error Description: Invalid URI sent from client. |
The URI in the request is invalid or does not comply to the specification. |
Check the specification for the correct URI. |
|
Error Code: E561 HTTP Response Code: 415 Category: CFG Error Description: Unsupported Media Type Header |
The handleHttpMediaType is not supported. |
Content type header is incorrect. |
|
Error Code: E562 HTTP Response Code: 406 Category: CFG Error Description: Media type header not acceptable. |
The handleHttpMediaType is not supported. |
Accept header is incorrect. |
|
Error Code: E564 HTTP Response Code: 400 Category: CFG Error Description: Invalid schema content supplied or schema validation failed. |
Schema update request payload, json content is invalid. The request payload json content does not comply to schema defined. |
Check the schema for correctness and formatting issues. |
|
Error Code: E565 HTTP Response Code: 404 Category: CFG Error Description: Data field does not exist. |
The request sent for unavailable service configuration data. | Check if the service key or id used is valid. |
|
Error Code: E566 HTTP Response Code: 404 Category: CFG Error Description: NF Operational State not found. |
NF Operational status is not found. | NA |
|
Error Code: E567 HTTP Response Code: 404 Category: CFG Error Description: Operational State History not present for the limit. |
Operational State History for the limit is not found. |
NA |
|
Error Code: E568 HTTP Response Code: 404 Category: CFG Error Description: NF score not available. |
NF score not available. | NA |
|
Error Code: E569 HTTP Response Code: 400 Category: CFG Error Description: Peer identity must be unique |
Multiple peers with same identity is received. |
Make sure to use unique for every diam serverpeer. |
|
Error Code: E570 HTTP Response Code: 500 Category: DB Error Description: SQL Command Grammar Error |
SQL statement syntax issues. |
Check the logs for more details. |
|
Error Code: E571 HTTP Response Code: 500 Category: DB Error Description: Resource accessed in an invalid fashion. |
Database fetch failure. |
Check the logs for more details. |
|
Error Code: E572 HTTP Response Code: 500 Category: DB Error Description: Permission denied to requested resource on the database. |
Database access failed due to permission issues. |
Check the logs for more details. |
|
Error Code: E573 HTTP Response Code: 503 Category: DB Error Description: Database table or resource not accessible. |
Data retrieval from database failed. |
Check the database availability and connectivity. Check the logs for more information on SQL state. |
|
Error Code: E574 HTTP Response Code: 503 Category: DB Error Description: Transient database access issue. |
Data retrieval from database failed. |
Check the database availability and connectivity. Check the logs for more information on SQL state. |
|
Error Code: E575 HTTP Response Code: 503 Category: DB Error Description: Cannot acquire lock on database resource. |
Data retrieval from database failed. |
Check the database state and database. Check the logs for more information on SQL state. |
|
Error Code: E576 HTTP Response Code: 400 Category: CFG Error Description: Insertion or update of invalid records to database. |
Internal SQL transaction failures due to invalid records not matching table schema. |
Check the content shared in payload from where the content is formed for insertion or update. |
|
Error Code: E577 HTTP Response Code: 404 Category: CFG Error Description: Resource fetch from database failed. |
Exception occurred during resource fetch from database. |
Check the logs for more information on failures. |
|
Error Code: E578 HTTP Response Code: 400 Category: CFG Error Description: Invalid payload. |
Internal JSON format data formation failure or invalid parameters passed, or, empty payload is passed. |
Check for any missing required parameters in the payload or check for provided empty payload. |
|
Error Code: E579 HTTP Response Code: 400 Category: CFG Error Description: Invalid format of data |
Invalid payload. Parameter with number type is not set correctly. |
Check the number or integer parameters are correct in the payload. |
|
Error Code: E580 HTTP Response Code: 405 Category: CFG Error Description: Operation not allowed. |
REST API used does not support the requested operation type. |
Check the specification for the allowed operations for provided REST API in request. |
|
Error Code: E581 HTTP Response Code: 500 Category: CFG Error Description: Internal server error |
Unidentified internal server errors. |
Check the logs for more details. |
|
Error Code: E582 HTTP Response Code: 400 Category: CFG Error Description: Subscriber export ranges are not valid. |
The provided start range value is greater than the end range value. |
Provide the correct values for start range and end range. |