Settings and activity
103 results found
-
8 votes
George Harb
supported this idea
·
-
61 votesGeorge Harb
supported this idea
·
-
6 votesGeorge Harb
supported this idea
·
-
7 votesGeorge Harb
supported this idea
·
-
10 votesGeorge Harb
supported this idea
·
-
15 votesGeorge Harb
supported this idea
·
An error occurred while saving the comment -
4 votesGeorge Harb
shared this idea
·
-
58 votesGeorge Harb
shared this idea
·
-
15 votesGeorge Harb
supported this idea
·
-
18 votesGeorge Harb
supported this idea
·
-
58 votes
An error occurred while saving the comment George Harb
commented
Especially where the Atera Agent is restarting every minute and flooding the event log.....
George Harb
supported this idea
·
-
12 votes
An error occurred while saving the comment George Harb
commented
Add the ability for the agent to send event log entries to the cloud portal so events can be reviewed even if the agent is offline.
Provide the ability to filter and sort the events and to create alerts directly from the event being viewed.
George Harb
supported this idea
·
-
24 votesGeorge Harb
supported this idea
·
-
24 votesGeorge Harb
supported this idea
·
-
10 votesGeorge Harb
supported this idea
·
-
153 votesGeorge Harb
supported this idea
·
An error occurred while saving the comment George Harb
commented
One of the most important features of any RMM solution is the monitoring of hardware. Specifically, temperature of the motherboard, CPU and DISK. Atera has that capability right now and thresholds are fully customizable. But different hardware has different thresholds.
Within the Intel lineup, there are different thresholds for the i3, i5 and i7. And even within the same processor family, there are different thresholds for different generations.
Having one conservative threshold generates a lot of false alerts. And going the other way is risky. Creating different thresholds for different processor types and generations becomes a management nightmare giving that we can't create monitoring sets yet.
What would be great is if Atera built an AI engine that received temperature telemetry data from the agents and compared them against a database of specifications for each peace of hardware. This way, you only have to build it once and every client benefits from it.
-
38 votesGeorge Harb
supported this idea
·
-
21 votesGeorge Harb
supported this idea
·
-
7 votesGeorge Harb
supported this idea
·
-
7 votesGeorge Harb
supported this idea
·
Even if the end user removed the agent, sometimes you DON'T want the device removed from the portal. Other RMMs handle this by marking the device as "Removed by end user".