Hi Site24x7 Team,
as mentioned
in other threads we are more and more increasing our footprint at
AWS. We deploy on an daily bases EC2, RDS and ELBs in different
Regions and multiple AWS Accounts. Currently we use the following
Features of Site24x7:
1) Auto-Discovery
by Site24x7 RO AWS User for multiple Accounts with Threshold /
Monitoring of RDS, EC2 and ELBs.
2) Installation of
Site24x7 Linux & Windows Server Agents
3) development
of our own plugins and related them to the Server Agents
4) End2End Measurements by Website Monitors
5)
End2End Transaction Checks by RealBrowser Measurements
6)
development of our own Actions to react on status changes
For us is Automation key - and API is King!
That means, for Installation, Updates and Configuration, we need
simply an comprehensive solution, what enables us to use the API
instead of an GUI like the Web interface of Site24x7.
Everytime when we need to interactively use the GUI, we do act
as an human bottleneck. Imagine, it takes us just an trigger to
deploy let's say 100 Servers in multiple regions. The deployment
itself is done after 10 Minutes. Now imagine, we would need to
configure the site24x7 Monitor for every single Server Monitor via
the GUI. Thats just an overkill.
So,
therefore I would like to ask you to pick up the following feature
request to support the comprehensive API support. I am pretty sure,
that's an invest in the future and let your customers like us
scale with site24x7 as we can scale out with the cloud.
1) SERVER AGENT
a)
Monitoring ID:
it is really required, that the
monitoring_id is available immediately on the local machine (where
the agent has been installed) after the Agent has been installed.
Today we need to download the whole list of all monitors from the
API and seek for the just installed Agent. That is horribly error
prone. Please add an feature to your agent, that it will get
it's own Monitoring_ID and store it anywhere in the local file
system (like /opt/site24x7/monagent/monitoringid.txt) or export the
ID to the env variables.
b) Process
monitoring / custom configuration template:
It is
absolutely mission crucial to add specific processes to the
measurement. Right now it is just possible via the GUI. Please
update the API that we can add/modify/remove Processes to the SERVER
Agent measurements
c)
Version Control / Update Agent feature:
It would be
helpful to get an overview of the different and current versions of
the site24x7 server agents installed out there in the field. Even
better, each Server monitor should have this version as string,
readable via the API. It would be furthermore helpful to be able to
trigger the update of all / list of agents remotely, by just an API
trigger.
2) OTHER
a) support customer owned
BulkSMS
We like that you support 3rd endpoints for alarms
like Slack. Even better would be, if we could use our own enterprise
BulkSMS Account instead of the Site24x7 SMS. Today we use for that
purpose the ACTIONS, but a transparent integration in the
userprofile would be better and less error prone.
b) SSO with an 3rd Party
IDP
With growing teams, especially of different vendors and
companies, it would be cool if an 3rd Party IDP like OKTA would be
supported.
c) AWS API calls with
Site24x7 ACTIONS
d) Published Reports, periods
adjustable by the viewer
We predefine a lot of Reports
and Status Pages. However, it is quiet sad that we have to define an
fixed period before we create the URL of the Report to share with
our clients. It would be much better, if we could share an Report,
and the actually viewer of the published report link could adjust by
and switch the period, let's say today, last week, this year etc
pp..
So, thats for now what would really
improve from our point of view the already excellent portfolio of
your Monitoring SaaS. Keep going folks, you are doing a great
job.
cheers
Markus