Your DX O2 Services are showing with "Unknown" Health status, the Services are based on UIM data and probes has been configured with a 10 minutes internal.
The reason of this issue in related to defect SLI Sum Operation is Operating on the Wrong Dataset DX O2 only support 5 and 15 minutes interval data processing.
Starting with 24.2HOTFIX 4, a new configuration capability has been introduced to adjust all the metrics that are received at a 10-minute interval to a 5-minute interval, Previously, metrics arriving at a 10-minute interval were aligned to a 15-minute interval. This configuration is global and will be applicable to all the metrics that will received at a 10-minute interval. This ensures consistent and accurate aggregation by the SLI sum function, eliminating over-counting and ensuring compliance with NASS metrics service standards.
This KB covers step by step instructions how to apply a resamping configuration required to enable fix availabe with HF#4
DX O2 24.*
Collect the internal token for authentication:
Steps to get internal Token.
Step-1:
Go to the Kubernetes terminal and run the below command
kubectl get pod| grep -i servicemanagement
Step-2:
Go to inside the pod using a below kubernate command.
kubectl exec -it <Name of service management pod> -- bash
Step-3:
Now run the below command to get the internal token.
cat /apmservices.sec/bootstrap.properties | grep apm.security.internalToken | sed 's/apm.security.internalToken=//g'
Endpoint:
POST <apmservices-gateway>/configuration/store
Authentication: This endpoint requires a valid internal token for authentication. This token should be included in the request headers as:
Authorization: Bearer <internal_token>
Description:
This endpoint stores a resampling configuration with a global setting. It defines the 10-minute resampling process to 5 minutes, which operates with a internal token.
Request Payload:
{
"key": "apm.nass.processing",
"value": {
"store": [
{
"id": "10MinResample",
"type": "resample",
"filter": {
"interval": ["10m"],
"type": "1"
},
"parameters": {
"target_interval": "5m"
}
}
]
}
}
Users can use this API to validate whether the configuration is saved or not
Endpoint:
POST <apmservices-gateway>/configuration/query
Authentication: This endpoint requires a valid internal token for authentication. This token should be included in the request headers as:
Authorization: Bearer <internal_token>
Description:
This endpoint queries the configuration based on specific filtering criteria. It’s used to fetch the stored resampling configuration
{
"filter": {
"op": "OR",
"input": [
{
"op": "EXACT",
"keys": [
"apm.nass.processing"
]
}
]
}
}
Response:
Status Code: 200 OK