I am trying to collect system metrics in graphite using collectd on multiple nodes. For some nodes all the metrics are reflected while for the others only few of the total metrics are getting reflected in graphite.
I check the collectd logs nothing wrong appears there. Then on checking graphite/storage/whisper/collectd i found out that the metrics group is missing for that node.
My question is what must be happening here and what should I try next in order to resolve this issue.
Related
The command
.show ingestion failures
outputs errors in the ingestion process. I however did not find a way to get list of successfully ingested items, as well as inspect the ingestion queue (names of the items) and current status (what is being ingested at the moment). Is it possible and how to view that information?
ADX is optimized for high throughput, therefore it is not optimized for exposing individual ingest operation tracking by default (that level of granularity puts extra load on the service).
We also do not expose detailed information on the queues, definitely not listing the ingress queue items.
You can track all the ingest operations (failed/succeeded/both) by setting up Diagnostic Logs with Azure Monitor.
An aggregated view on your cluster via metrics is also available.
Please see Monitor Azure Data Explorer performance, health & usage with metrics and Monitor batching ingestion in Azure Data Explorer.
We are building a tool to off-board existing employees, including clearing their calendars of all existing events. When querying the /calendars/{calendarID}/events/ endpoint, we are occasionally getting a 500 - Stack limit exceeded error. We're only generating a few dozen to hundred requests, so we don't seem to be hitting any rate limits, which appear to be 10k per day; additionally, it's only intermittent, rather than a failing continuously, as a rate limit would generally cause. Anyone familiar with this error?
You can find all the Calendar API related errors by checking this link here.
As for the error message 500 - Stack limit exceeded you are receiving, it looks like the issue might in fact be coming from somewhere else.
You can also test the Calendar API by using the Calendar API Reference here.
Reference
Calendar API Errors;
Calendar API Events:get.
I am using hosted graphite and statsd. I want to reduce the costs, by reducing the metrics been sent.
For example: for each timer, I don't want to send all 14 metrics (upper, std...), but only 3 of them (mean_90, sum, and maybe another one).
How can I configure that in the statsd configuration file?
Looking at the statsd docs and its source, I don't think you can configure it to not send all the metrics.
I suggest that you either:
Edit the source code to only calculate and send the metrics you want. This is probably easy to do just deleting the lines where they are calculated.
Configure Graphite to drop all metrics coming from statsd not matching the three patterns you want.
Since last two days I am receiving a dailyLimitExceeded error on one of the Profiles that I run queries on - even if I run it early in the day. I understand happens when there are more than 10000 queries for the same profile in the day. As far as we have researched internally, no known process from our company is sending such a large number of queries for this profile via APIs. Is there a way to find out what is causing this problem?
ProfileID = ga:64708881
Is it possible to find out the source of queries for this profile that is leading to dailyLimitExceeded error?
I am developing an app to show real time prices of cryptocurrencies. I am using Firebase open data set.
If my app suddenly gets disconnected from network (no carrier connection or wifi), then on re-connection, will Firebase sends all the price changes that app missed while it was disconnected? For example, my app got disconnected at 1PM and then re-connects back at 1:30pm and lets say Bitcoin price changed 15 times during this period. So when I connect back at 1:30PM, will I get all the 15 prices changes and in the right order?
In this specific case, probably not.
Firebase focuses on getting your app synchronized with the most current value. If a given node changes a lot, it's going to catch your client up on the state rather than playing back a log of change events.
In other words, the open data set that you are using is not designed to create a time series chart. Instead it's designed to show you the most recent value.
To accomplish your goal you need a Firebase that synchronizes historical data instead of just the simple value. For example, Firepad, a collaborative text editor, uses a technique called operational transformation to solve a similar problem.