Tom_S-L
Joined 10 years ago
User Profile
User Widgets
Contributions
Re: Three hosts, one service check?
On 6/20/2018 at 9:47 PM, Kerry DeVilbiss said: @Tom S-L - using our internal website checks (with multiple collectors as checkpoints,) you could check the JSON path for that specific datapoint to make sure that '0' is not present - and alert if it is in fact found (on a certain number of collectors of those you have specified.) For example I think that should work for the use case you've outlined. And just in case it's helpful, here's a set of links to the more advanced creation of scripted internal website checks: Documentation for Executing Internal Web Checks via Groovy Scripts Documentation on Groovy HTTP Access Documentation on Web Checks with Form-Based Authentication Blog post on Scripted Internal Website Checks Cheers, Kerry Thanks Kerry, this is a good start. As stated I need to check datapoints from multiple servers and alert if, say, 2/3 had an issue. If I can pass the result on to more steps then this will work as a website check.13Views0likes0CommentsThree hosts, one service check?
Hi, I have a datasource that uses a regex to pull values out of some JSON and graphs numerous values. This runs on multiple hosts and the host goes critical if a particular value hits 0. I don't want the individual servers to go critical, I'd like a service/website check to go critical if two out of three sites return the zero value in their JSON response. I can write a datasource to check the JSON from each site but then I have to apply it to a host, or multiple hosts, and that defeats the point as I don't care if a single one goes away. Is it possible to create a website check that takes in the JSON, extracts the data required, then passes it on to be used in another step which checks the next site, can I alert on values within the response? Is this even the right way to do it? It would be great if a datasource could be run from a collector group rather than tied to a specific host!29Views0likes2CommentsRe: Overlay Alert Thresholds on graphs
Just going back through some older posts...We 'solved' this by adding virtual datapoints woith static values to custom graph widgets on our dashboards. Although not ideal, and certainly doesn't turn the background a different colour, it has sufficed in our case.1View0likes0CommentsCustom Graph Widget Line Colours
Can someone explain logic for when I can and can't change line colours on the custom graph widget? Some I can change quite happily but on others the 'Color' drop down option is set to auto and greyed out. this is maddening when I have multiple lines, stick a virtual datapoint in for an SLA line and can't change the colours so they all match (for example).6Views0likes1CommentRe: Dimensionless Cloudwatch Metrics
...Additionally, why is the query (even the working one) giving "Statistics: [Average, Maximum, Minimum, SampleCount, Sum]" when I've specified Average/Sum? ...and how do I change the "Period: 60"? Specifying period manually for the datapoint isn't updating the query shown in Poll Now. :)/emoticons/smile@2x.png 2x" title=":)" width="20">5Views0likes0CommentsRe: Dimensionless Cloudwatch Metrics
19 hours ago, Sarah Terry said: The CloudWatch collection mechanism should work with dimensionless metrics - have you tried using the Poll Now feature? You can see it on the raw data tab for the DataSource, and it should display any errors returned by AWS, as well as the request LM is making to AWS (so you can see if, e.g. the aggregation method is being incorrectly passed as a dimension). We'll do some testing on our end to confirm data collection works for dimensionless metrics & put up an example in the docs. Hi Sarah, Yes I've tried the Poll Now feature, It gives an HTTP status code of 200 with Error Code/Message both showing None. Both tried around 13:00 BST, request descriptions as follows: Not working (NaN) but returning HTTP200 and no errors: Metric Path: SBProxy>E2EMetric>Sum Req Desc: {Namespace: SBProxy,MetricName: E2EMetric,Dimensions: [],StartTime: Wed Sep 06 04:30:00 PDT 2017,EndTime: Wed Sep 06 05:00:00 PDT 2017,Period: 60,Statistics: [Average, Maximum, Minimum, SampleCount, Sum],} Working Metric Path: SBProxy>AutoScalingGroupName:##sbbroker_asg_name##>FileSize>Average Req Desc: {Namespace: SBProxy,MetricName: FileSize,Dimensions: [{Name: AutoScalingGroupName,Value: [ASG_name_here]}],StartTime: Wed Sep 06 04:30:00 PDT 2017,EndTime: Wed Sep 06 05:00:00 PDT 2017,Period: 60,Statistics: [Average, Maximum, Minimum, SampleCount, Sum],} A dimensionless example in the docs would be great thanks.0Views0likes0CommentsDimensionless Cloudwatch Metrics
I've been creating datasources to collect our custom AWS Cloudwatch metrics as per the docs: https://www.logicmonitor.com/support/monitoring/cloud/monitoring-custom-cloudwatch-metrics/ - mainly this is fine... However it can't cope with dimensionless metrics: " Namespace>Dimensions>Metric>AggregationMethod , where Dimensions should be one or more key value pairs" I've tried creating datapoints without a dimension but it returns NAN (probably because LM requires "one or more key value pairs" for dimensions). We currently use a Python script to collect most our custom metrics but it's resource intensive for our collectors and I'm trying to move away from it. Does anyone know of a way to use the 'AWS CLOUDWATCH' collector with dimensionless metrics?19Views0likes5Comments