You need to have a way of determining which targets to scrape from the information returned from the EC2 service discovery call.
The main details are tags, but you can also use AZ, instance type, platform, subnet, VPC. So as long as you can differentiate using those then you can create relabeling rules to scrape what is needed. If not, you'd need to change something about the instances to be able to - normally the easiest is to add a tag for each job to scrape the target for. On 1 March 2020 15:11:20 GMT, rs vas <rsvas.t...@gmail.com> wrote: >Hi, We are trying to trace JMX exporter metrics from EC2 instances in a > >given AWS account. We are using EC2 service discovery option to >discover >the targets in AWS account. > >But the challenge here is some of the nodes showing as DOWN where JMX >exporter is not running. Applying Tag is not an option on those >instances, >then is there any other configurations we can make in prometheus.yml >which >would ignore the instances don't have JMX exporter running? Appreciate >any >input on this. Thanks! > >-- >You received this message because you are subscribed to the Google >Groups "Prometheus Users" group. >To unsubscribe from this group and stop receiving emails from it, send >an email to prometheus-users+unsubscr...@googlegroups.com. >To view this discussion on the web visit >https://groups.google.com/d/msgid/prometheus-users/f254d16d-6b7d-48dc-8d6b-9116b8be2ece%40googlegroups.com. -- Sent from my Android device with K-9 Mail. Please excuse my brevity. -- You received this message because you are subscribed to the Google Groups "Prometheus Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to prometheus-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/prometheus-users/47702F8A-9BDD-4D92-A2F3-E274C74DE187%40Jahingo.com.
