Jake, On 8/21/2020 10:26 AM, Jake Orel wrote: > Hey Chris, > I've been working with Jerry on this. What I had found was to use Collectd > with the java and genericJMX plugins to gather the Mbeans i wanted to send. > After that there was the options of either using a cloudwatchPlugin > <https://github.com/awslabs/collectd-cloudwatch> for collectd or using the > AWS Cloudwatch agent to collect the metrics from collectd and send those to > cloudwatch. I've been able to get basic ec2 metrics (memory-free, > memory-percent-used, disk-used) from both of those angles but neither one > has let me send the JMX to cloudwatch. I don't seem to be getting any error > messages from either of them and they both tell me they're running. > <https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/CloudWatch-Agent-custom-metrics-collectd.html> > > On Fri, Aug 21, 2020 at 11:34 AM Christopher Schultz < > ch...@christopherschultz.net> wrote: > > Jerry, > > On 8/19/20 13:19, Jerry Malcolm wrote: >>>> Is anyone successfully monitoring Tomcat JMX beans on Amazon >>>> CloudWatch? This shouldn't be that difficult. But we are hitting >>>> a brick wall. Can't get anything to work that is recommended on >>>> forums. > > What have you tried so far? > > -chris
Seems like fluentd would be another approach. I haven't tried it yet, but the following links look promising. Cloudwatch - albeit with a Kubernetes cluster https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/Container-Insights-setup-logs.html Fluentd JMX plugin https://github.com/hidsuzuk/fluent-plugin-jmx/blob/master/README.md This looks workable, although it may be a bit heavy for a per-EC2 implementation. I'm slowly working on dockerizing and containerizing a bunch of applications running on Tomcat. This is the monitoring approach that I'm considering. . . . just my two cents /mde/
signature.asc
Description: OpenPGP digital signature
