You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello,
When an app xxx is running and I want to know the active sessions, I see at jmx level that the next Mbean: jboss.web:type=Manager,host=localhost,path=/xxx have the attribute Name "JBossCacheManager", and then the activeSessions attribute not exist, but ActiveSessions yes.
Do you have any tip to configure zorka / zabbix to manage this circunstance with your zabbix.discovery["jboss", "jboss.web:type=Manager,*", "type", "host", "path"] function ?
I'm thinking on duplicate the discovery rule and to apply to this second discovery rule a filter, and then change the attribute names to its equiv but the first letter with capital letter.
Thank you for zorka!
The text was updated successfully, but these errors were encountered:
I solved this issue by creating two discovering rules (ideally cloned at start), and applying different filters, one for JBossCacheManager and other for StandardManager, and then changing the propertie, and playing with spaces
Hello,
When an app xxx is running and I want to know the active sessions, I see at jmx level that the next Mbean: jboss.web:type=Manager,host=localhost,path=/xxx have the attribute Name "JBossCacheManager", and then the activeSessions attribute not exist, but ActiveSessions yes.
Do you have any tip to configure zorka / zabbix to manage this circunstance with your zabbix.discovery["jboss", "jboss.web:type=Manager,*", "type", "host", "path"] function ?
I'm thinking on duplicate the discovery rule and to apply to this second discovery rule a filter, and then change the attribute names to its equiv but the first letter with capital letter.
Thank you for zorka!
The text was updated successfully, but these errors were encountered: