Out of box Health check process fault not executing

Tagged: Healthcheck

- sandeep.mohanty
  Participant
  
  2 years, 7 months ago #3282
  
  We are unable to trigger/call ignio Cheetah healthcheck at process fault which is a requirement based on existing Butterfly use case.
  
  Since we have existing healthcheck use case for important client segment uses process fault, there is need of solution to migrate the same end-to-end use case to new Cheetah platform. Please advise how process fault can be implemented in healthcheck.
  
  Cheetah version 2.4.1
- umangrdoshi
  Participant
  
  2 years, 7 months ago #3283
  
  Up
  0
  Down
  ::
  The entity for which health check is to be configured is a Windows process.
- vilok0806
  Moderator
  
  2 years, 7 months ago #3284
  
  Up
  0
  Down
  ::
  Hi Sandeep,
  
  Process fault (pattern) will invoke check faults (aka health checks) on influencing entities while triaging. If the required blueprint topology is present health checks will get invoked.
  
  Health check is slightly separate use case, it is purely checking and detecting faults. So you can trigger it on-demand or schedule it. Whereas Process fault is in response to an issue attempting to triage/resolve it.
  
  If you want to resolve a fault that is detected during HC, you can configure it by setting the “Fault Triage policy”
- umangrdoshi
  Participant
  
  2 years, 7 months ago #3285
  
  Up
  0
  Down
  ::
  Hi Jackson,
  
  The requirement is for an independent (separate) HC. for process as an entity. Is it possible to trigger / schedule for a process to check if the status is running or not?
- vilok0806
  Moderator
  
  2 years, 7 months ago #3286
  
  Up
  0
  Down
  ::
  Umang,
  
  I got it mixed with process fault while you wanted to trigger HC on a windows process.
  
  You can blueprint the process entity, process name is the key which I believe will not change. You can schedule HC on it (Actions –> Check Health).
- sandeep.mohanty
  Participant
  
  2 years, 7 months ago #3294
  
  Up
  0
  Down
  ::
  Thank you Jackson and Umang. Yes, Process name will not change. Will try modeling process entity and share the results.
- vilok0806
  Moderator
  
  2 years, 7 months ago #3296
  
  Up
  0
  Down
  ::
  Hi,
  I believe you meant blueprinting the entity and not modelling it. There is an OOB entity named OSProcess.
- rishabh.verma
  Participant
  
  2 years, 7 months ago #3297
  
  Up
  0
  Down
  ::
  Hi Jackson and Umang,
  
  We have already tried blueprinting “OSProcess” entity under Windows entity and run “Check Health” Function, still for Process no fault runs. Similar thing we tried with Service and fault for checking service status executed successfully.
  
  Policies Applied : Credential, Associated Connector, HealthCheck Policy.
  
  Thanks & Regards,
  Rishabh Verma
- arumuganainar.s
  Moderator
  
  2 years, 7 months ago #3306
  
  Up
  0
  Down
  ::
  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.