We have a strange issue with Stackdriver alerts in our project. We have set up an alert that triggers if a log metric falls below a threshold, and just recently it has triggered an alert despite the logs being normal. The graph in the alert page shows that there are 2 metrics being measured (there should only be 1), and that one of them falls down to 0, and then a new one with the same name 'takes over'. It seems that the alert is triggered for the 1st one, but since the 2nd one proceeds as normal, the alert for the 1st one never resolves.
The screenshots show this 'transition' in the graph. At 8:57pm, the 1st graph is at 0 and the 2nd graph at 0.53. Then at 9:03pm the 1st graph has risen to 0.42 and the 2nd graph has fallen to 0 and has remained at 0 for the past few hours, which triggered the alert. How do I resolve this alert?
There has been an issue on our side that created to 2 metrics and one of them was triggering the alert.
This issue could have affected more customers, but we did not provide any specific solution to this post as it has been a transient issue and it has been fixed to all customers.
Related
I am trying to create a trigger that will run after 20 seconds of no user activiry on page.
It works simply in theory but I couldnt find any solution of how to do that.
By no activity i mean no click ( gtm.click ) happening in that time.
Thanks a lot for your help :)
I would advise you to create a Timer trigger. You'll specify a name for the event that's used when it elapses (defaults to "gtm.timer", the interval at which it fires (in milliseconds) and an optional limit to cap how many times it fires (leaving it blank means it won't ever stop firing each interval).
You're describing a scenario where it should fire a single time at 20 seconds, so you'd want to configure it as in the following:
We're implementing Google Analytics in retail consumer kiosk software. There is no Javascript or SDKs or web pages involved - we craft a URL per Measurement Protocol and post it. We find that sometimes hits seem to just stop getting counted. If we watch the Real-Time section on the GA web site we can see that our hits continue to get posted, but over in the Behavior / Screens section the number of screen views for this device for today stops incrementing.
It's not just a "sometimes you have to wait 24 hours" thing, because Tuesday and Wednesday of last week still show zero today. If it's a rate limit, I can't see what - we're nowhere near 200k hits per day (per user, but from our point of view each kiosk is a user - we don't have any means to identify individual users); we shouldn't be hitting 500 hits per session because we send a session start (ec=Session&sc=Start) each time the user does something on the main menu and a session end (ec=Session&sc=End) each time the workflow finishes, which shouldn't ever be more than 20 screens - the default 'idle timeout' definition of a session wouldn't work well for us since a user can legitimately be working on a single screen for 10 minutes or more editing a picture whereas also a user can finish and leave and the next user in line start using the kiosk within just a few seconds; we shouldn't be sending events 'too fast' because it takes a couple seconds for a human to read the screen and reach out and touch a button.
What we observe is that some days it counts up to 340-360 and stops and some days it stays at 0 permanently. Any idea what's happening and how to fix it?
11/24: Today it went up to 352 and then stopped. This was about one hour of activity. All of this has been done with "Highest precision" selected.
12/1: Still same, counts for about one hour, to 347 screen views today, then stops incrementing.
When I look at Audience/Overview it says "Sessions 1". There should be dozens of sessions, split up by when we send (ec=Session&sc=Start). I think it must not be recognizing that as a session, it must be using the session timeout (idle), and staying all within a single session, and therefore limiting to 500 hits (we've got some events to go along with the screen views). And this is just wrong. Session should end when we say it does.
12/1: One correction, we actually do send sc=start and sc=end, with the values lower-case, as specified by Google.
My coworker did some experimenting and found that sc=start is ignored on t=event hits. It is recognized on t=pageview hits. I changed my reporting a bit to generate a fake pageview when a session starts, just so I could send the sc=start, and now the counts are accurate.
I am trying to setup a notification to occur when:
The current amount of Users, today is greater than that of the previous day's.
For instance.. If yesterday shows as having 500 users and today, at 5 o'clock PM, there are 501 users... Is there anyway to send out a single notification as soon as the threshold is broken... and not for every single new user after that threshold?
Closest thing would be a custom alert (via intelligence events->custom alerts or admin->tools and assets->custom alerts).
If you set this up as a daily alert it will be sent only once per day. I have never tested this with absolute numbers (only with "increases by %" as condition), but since the option is offered in the interface I guess it should work.
Good day, I'm confused about the real-time's graph. it minimum is 1 hour. and the graph refresh almost 30 seconds at a time , can we change it to be more real-time,just like 2 or 3 second.
And I try to rewrite the item Update interval (in sec), it's not useful, I try google and know that it means the interval the agent collects data from the OS or some other place.
So Basically, Who can tell me how to change it? it can't support to change?
Every response will be appreciated!
You should go to your profile (in the upper right corner) and change "Refresh (in seconds)" field to your preferred value.
I have problem with sending event to Google Analytics.
In some cases the event label is empty.
I can see the label in fiddler.
The category and action are always saved.
It seems as if it happens to label that are sent in low numbers.
Is there a limitation in Google analytics that it omits the label if the count to that label is relatively low and there is a lot of other traffic?
My site has a lot of traffic, millions of events per day
Once the number of data points crosses a certain threshold (depending on the report type) , GA uses sampled data to reduce the load on their servers.
To see if a report is sampled, look for a checkerboard-like icon in the upper right corner of the interface. You can click this to access a slider to increase the amount of data in a sample, but only to a certain point.
Check to see if your reports are being sampled. If so, it may well be that a label with a small number of data points gets totally overlooked and therefore shows up as zero in the sampled report.
If this is indeed your problem, you can decrease the date range until you no longer see the sampling icon.
Yes, in G4 they are now missing.
These are user fields (self made).
Also missing browser version. What a shame for Google.