Naveenkumar
NeophyteJoined 2 years ago
User Profile
Neophyte
User Widgets
Contributions
Re: Issue in auto refreshing EC2 properties
Hi Mike, 1. Even after 12 hours the alert on Win_WMI_Access_Denied_ErrorCodes check on port 135 is not cleared after it started working. 2. Using Wbemtest from collectors to make sure wmi can be accessible from the collector. 3. Also using the debug console with explicitly mentioning the wmi username and password can get the metrics but if I run the debug command without mentioning creds it gives access denied error. 4. After that I'm clicking on refresh properties button as mentioned in the screenshot. 5. If I reload the device page all the missing datasources are applied, Alert is cleared, metrics started to poll.18Views0likes1CommentIssue in auto refreshing EC2 properties
I’m encountering an issue with my Windows ASG group EC2 instances. Whenever a new instance is added, certain properties from a dynamic group—most notably “wmi.user” and “wmi.pass”—are applied. However, by the time the instance is registered in LogicMonitor, WMI isn’t immediately available because some automations are still configuring the WMI credentials on the host. A few minutes later, WMI starts working on the host, and I can successfully test it using wbemtest from the local collector. However, the LogicMonitor portal still shows that WMI is not responding. Interestingly, when I use the collector’s debug console and explicitly specify the WMI credentials, it pulls the information successfully. But if I don’t specify the credentials manually, it fails to work. The only way to resolve this is by manually running “refresh properties,” after which WMI starts working without making any changes. I’m trying to figure out if there’s a way to automatically force a properties refresh every 15 minutes to ensure everything works as expected without manual intervention.46Views2likes3CommentsRe: Any way to pull available upgrade collector version via API,SDK or any other means.
Hi @LMjosephBrett Thanks for your info. Also, I’m assuming. stable: false & mandatory: false refers Early Release stable: true & mandatory: false refers General Release stable: true & mandatory: true refers Mandatory General Release Is this true by any chance?13Views3likes0CommentsMonitoring Ec2 instances
Hi All, I have been going through the documentation and it suggests that when we are setting up monitoring for ec2 with autoscaling we should select netscan frequency of 10 minutes. This is the minimum time we can configure and new device may take upto 15 minutes to be monitored. My question is is there a way if a new instance is launched we can bring that into monitoring less than 10 or 5 minutes.90Views7likes1CommentRe: Does anyone aware where I can find AWS cloud watch API call logs in AWS account or from LM?
Hi @Tushar Kadam , Thanks for your detailed explanation, I still have a doubt that, If I add a device there will be at least 1 Data source and that data sources has many data points, My question is for 1 API call for 1 data source or for each Data points there will be 1 API Call?19Views1like0CommentsDoes anyone aware where I can find AWS cloud watch API call logs in AWS account or from LM?
Does anyone aware where I can find AWS cloud watch API call logs to collect metrics from LM account like cloud watch or cloud trail? I wanted to know how many API calls made to the aws ec2 service for a particular ec2 instance in given time to collect metrics.Solved133Views11likes3CommentsRe: Does cloud watch API calls bound to Data Sources or Data points?
As per the above document, Total Number of Metrics for 1 EC2 is 95,404 for 11 data points, if i have unchecked 5/6 datapoints the total metrics to be collected will be reduced to around 45-50k requests, and the cost would also be proportional to number of request, so the cost should be around $0.40 - $0.60. Correct me if i’m wrong. @Michael Raymond AWS Service Number of Datapoints Polling Interval (min) Total Number of Metrics Request per Month (60 min/hour, 24 hours/day, 30 days/month) CloudWatch Charge Rate Estimated Additional Cost per Resource per Month EC2 11 5 95,404 $0.01 per 1,000 metrics requested $0.954Views0likes0Comments