If you're talking about this: ELK Stack: Elasticsearch, Logstash, Kibana | Elastic, we have not had the chance to integrate with it but it looks like you can reach out to it using API and REST API so you should be able to use AI to integrate to it.
Thanks Louis for your reply, I will check on this.
also if you could guide me, let's say if we are setting up a new monitoring so what all things to manage for an example tickets should be raised for any control-m server/EM server/Agent unavailability in that tool
than about the jobs failure/late execution stuffs like that, I mean is there any specific path or way to manage this.
thanks in advance
Multiple ways you can raise a ticket when an agent become unavailable:
- Many server monitoring tools exist on the market to monitor the status of your servers (disk space, CPU, processes) so if you have one of those, you can use it to monitor the agent process on your host
- Setup SNMP trap on xalerts in Control-M
- Set up a job in Control-M to ping your agent and send an alert when it is unavailable
You can reference this other thread in the BMC Community for more info: Need to have an email alerts from Control-M when agents become unavailable
Our firm has created scripts to integrate Control-M and PagerDuty so if you use PagerDuty, we can help you.
Oh Thanks much! Appreciate your reply.
Do you have any kind of documentation or help me to get one, as at my side we are looking for the same integration of Control-M with ELK.
Hi nicolas wood
Thanks for sharing these examples! ELK is new to me, and maybe to other Control-M users, but as it is so popular I'm sure many are being asked to try and use to gain insights from Control-M data.
In your setup, do you use FileBeat/Logstash to:
* extract data directly from Control-M database?
* or do you extract it using AAPI calls?
* or do you extract it to files (maybe using reports) and then have the files fed into Elasticsearch?
Also, do you mind sharing details regarding the server that hosts ELK for the Control-M data?
* Is it dedicated to Control-M data only?
* What specs have you given it?
* Is ELK on the same host as Control-M or on its own host?
* Roughly how much data and at what frequency do you feed into ELK from Control-M?
(I'm trying to gage what size server I would need to run ELK in my environment, where Control-M has ~500K jobs loaded per day and about 1.5mil executions per day)