Forum Replies Created
-
arumuganainar.sModerator3 years ago in reply to: Application Health check by AIOps without awindows admin access #3367::Currently ignio needs local administrator privilege in the target servers in order for it to connect to the target servers. It does not need domain admin privilege. Though the health commands are read only, ignio needs local administrator privilege to connect to the target server through powershell remoting.
From SP7, ignio will not need local administrator privilege as it can support Powershell JEA configuration.
JEA Prerequisites (in short):
List of things to be enabled in target machine(s):
• PowerShell 5.0 or Windows Management Framework 5.1 or higher
• Define Role capabilities
• Define Session Configuration
• Register the JEA ConfigurationIn Connector Policy:
• Configuration Name of JEA should be specifiedarumuganainar.sModerator2 years, 11 months ago in reply to: How to configure Custom Faults for Health Check fault selection policy ? #3458::Hi, this is not available in SP6. That is, in SP6, custom faults are not considered in HC fault selection policy for Windows and Linux. It will work for other technologies. We are considering this enhancement in SP8.
arumuganainar.sModerator2 years, 11 months ago in reply to: When to use Associated Connector policy #3493::This associated connector policy should be attached to the node if the function code body is implemented in any of the target languages such as bash, powershell, cisco commands etc., If the function is implemented in groovy, then there is no need to attach the connector policy. That is, if ignio needs to connect to the target machines to execute the function, then we need to attach the connector policy. The functions implemented in groovy are executed on the servers where ignio (core) is installed or on the proxy agent machine. So, for the the groovy functions, ignio does not use any connectors.
arumuganainar.sModerator3 years, 1 month ago in reply to: Out of box Health check process fault not executing #3306::Hi Rishabh, the OSProcess entity is volatile. So, we can’t blueprint this entity. HC is executed only for the entities that are blueprinted. If it is really a process (not a service) and if you want to do the HC, please create a custom non-volatile entity for your process, model the fault by adding “HealthCheck” tag and implement the checkFault function.
arumuganainar.sModerator3 years, 1 month ago in reply to: Healthcheck triggers email report only in case of fault #3307::Hi Sandeep, it is possible. Please refer the below mentioned confluence link.
https://digitate.atlassian.net/wiki/spaces/ID/pages/1733165144/Enhancements+in+SP6
arumuganainar.sModerator2 years, 11 months ago in reply to: How to configure Custom Faults for Health Check fault selection policy ? #3463arumuganainar.sModerator2 years, 9 months ago in reply to: Impact of Downgrading Bundle to lower version #3574::Hi, There is no impact on the existing entities or policies. Few functions are added in 2.49.11 when compared to 2.7.8.
arumuganainar.sModerator2 years, 9 months ago in reply to: Healthcheck Report Ellaboration #3579::Hi,
Health Check Pattern functionality and dashboard related information is available in the following link.
https://digitate.atlassian.net/wiki/spaces/ID/pages/1935999951/Healthcheck+SP6
Health Check faults for technology level can be found from following links.
https://digitate.atlassian.net/wiki/spaces/ID/pages/1936000217/Healthcheck+Technology-wise+Use+Case+Guides+SP6
https://digitate.atlassian.net/wiki/spaces/ID/pages/903905389/Healthcheck+User+Guidesarumuganainar.sModerator2 years, 9 months ago in reply to: Coloring in Healhcheck Report #3580::Hi,
Yes. We already have this feature in Cheetah SP6 HC dashboard.
Red – Critical
Amber – Warning
Green – OK
Grey – Unable to Checkarumuganainar.sModerator2 years, 6 months ago in reply to: Population of various columns of HealthCheck Report #3664::Please check “Sample Healthcheck Process and its Modeling” section in the link below.