Host anomaly detection settings are not applicable for PaaS or standalone deployments

[tijust1]

Hi,

Under the host monitoring, i am seeing message "Host anomaly detection settings are not applicable for PaaS/standalone deployments." what does that means. 

[Mizső · Accepted solution]

Hi @tijust1,

I have only managed PaaS implemantations (some Solaris systems). I thnik at PaaS implemantation only the process is instrumented, there is not any host level metric collection. So I thnik that is why you can not change the host level anomaly detection rules eg. host level CPU saturation and so on...

I hope it helps.

Best regards,

Mizső

[PacoPorro]

Correct. 
Platform as a service abstract user from the OS. Oneagent PaaS implementation is about the process not the OS

[Romanenkov_Al3x]

Helpful, thanks!

[tijust1]

@Mizső and @PacoPorro  Thanks for your message... I am clear not even that make sense too.

[dan_m_smith]

This raises the question of JVM level Anomaly Detection.  I find it odd that these have always been defined at the Host Level and not the Process Level  So on our Kubernetes platform running BottleRocket O/S (AppOnly deployment=Paas), we have no way to control the garbage collection anomaly detection settings.  If it as defined at the Process level this would not be a problem. 

Does anyone have a solution for this, other than Custom Metric Events and Process level tagging or naming.