Thank adivinho, The issue was since I enable Integrated alerting , the port was already in use , so I had to use a different port. I was able to start it with a different port.
Like you said , I started off using Intergrated Alerting but heard from the support that its not GA and still a technical preview and is not ready for production servers. Even otherwise, I’m struggling to make all the alerts work with Integrated Alerting. Like for eg. I get alerted when mysql is down but not for OS level alerts like CPU, Memory etc. I’m using the built in templates for now .
Have you been using it ? if yes , how did it go for you ? Please suggest what I’m missing that I can’t get alerted for OS level alerts .
Understood . One more thing I forgot to mention above is I’m not using a docker. I’m using the AWS AMI provided from the market place and I’m monitoring Aurora MySQL clusters. So it has to get the OS related information via the cloudmetrics . I checked and I think enhanced monitoring is turned on for the RDS instances . Anything else I could be missing here ? Is Integrated alerting even supposed to be working for AWS RDS Instances being monitored by AWS AMI from market place ? So far I do not have any custom alerts . I’m still working around with Built in alerts
Mainly all metrics names are equal for rds exporter and node, mysqld exporters.
But there is an exception for CPU usage. I will create a ticket for making build-in template “Node high CPU load” compatible with RDS metrics.
Other templates use compatible expressions.
We have to wait the next release when the issue is solved. It’s pretty hard to invent an alert without using symbol “less then”.
You may find metric names and descriptions in next test data files for rds_exporter.