User info
First name | Veerle |
Last name | Ledoux |
DevOps Program
Acquired rank |
Advocate
|
Points progress |
2627
DevOps Points
|
Here are a few tips to level up your DevOps game and unlock an arsenal of perks and benefits. | |
DevOps attestation | Request your attestation ID and expiry date |
Achievements
|
Questions asked
Answers given
Indeed, the suggestion events tab only displays recently detected behavioral changes or patterns in a parameter's trend data. However, the history of suggestion events can be retrieved in a very similar...
View QuestionHi Thomas, The suggestion events are created as information events, that is they have severity "Information", and with Source equal to "Suggestion Engine". In order to allow the correlation rule to be...
View QuestionTo check if the proactive cap detection functionality is enabled on your system, navigate to the Cube System settings > analytics config page. Additionally, there is a system-wide “Minimum alarm...
View QuestionThank you for bringing this situation to our attention. Some initial investigation on this system revealed a large number of suggestion events on table parameters “flatlining”. More recent versions...
View QuestionHi Bruno, The lengths of the predictions shown in trend graphs are indeed fixed. On each trend data aggregation level, we fixed the forecasting horizon to be at most 200 predicted points into the future....
View QuestionHi Paul, The current flatline detection functionality is based on a model that learns the normal range of time intervals between value updates of a parameter. When a value update takes too long and is...
View QuestionAs far as I know, the -1000 entry is an extra entry added as a gap start marker. It gets added by SLNet in an extra processing step on the raw trend data, when it is handling a GetTrendData request which...
View Question