G'day Ryan,
I received your reply to my question.
Per your reply, required APM Agent quantities is very small (below hundred) and it ain't worth building an on-premise set up just for APM for this customer. But, this answer is not the solution you are looking for, hence let's look at this as an Opportunity to establish strategic foot with this customer. And that begins with expanding beyond Silos, meaning, explore with customer beyond just APM. The potential other areas can be Digital Experience Monitoring, Network Monitoring, Infra Monitoring, AIOps & Automation.
You may ask but why not just APM on-premise for such a small estate, the rationale is, our solution is aligned to offer AIOps, Monitoring and Automation in a unified cloud agonistic platform (can be built on K8s or Openshift) and with it customer can optimize their spend with multiple point tools and benefit from a single unified platform solution which gives the collective intelligence across Digital customer experience (Mobile & Web), Modern APM, Infra Monitoring and NetOps with integrated Automation capabilities (self healing use cases) and have access to Service Analytics, Alarm Analytics, Performance Analytics and so on. Even, Industry analyst like Gartner too recommend having collective observability which comes via Domain agnostic AIOps solution which has data ingested via all possible Monitoring tools. If this conversation generates more interest with customer, your game elevates to next level which is APM + other solutions and that's an opportunity.
You will then have two ways to deliver it. Here are few Options for your consideration to bounce with customer!
Option1: Revalidate the exact reason with customer, why not DX SaaS?
Let's try to understand, is this customer strictly no-no for any SaaS solution? Meaning, customer doesn't even us any SaaS solution, e.g. Salesforce, ServiceNow? If that's the case we don't win with Option 1 however if there is any technical concern, we can definitely work towards addressing them and if that goes well, Option 1 is best suited for such small size customers.
Option2: Assuming customer, has skills to manage K8s or Openshift environments and willing to expand beyond just APM with other areas like AIOps and more, it makes sense to build an on-premise set up. Based on actual information, sizing can be determined.
Option3: Assuming customer is not willing to Expand beyond APM but open to a shared service platform in local region, that's when Your consulting firm can build a multitenant platform and on-board multiple small size customers in them. Based on actual information, sizing can be determined.
------------------------------
Enterprise Solutions Architect
Broadcom
------------------------------
Original Message:
Sent: 11-01-2020 06:46 PM
From: RYAN JOHNSON
Subject: Upgrading to DX APM 20.2 - need sizings for small installation on premises
Hi,
We are upgrading an existing DX APM 9.x installation (on premises) and are looking for realistic sizings for a small number of agents and metrics for a DX APM 20.2 on premises install. Documentation is very focused on large scale installations supporting thousands of agents/metrics. Any assistance or feedback from folks who have done this already would be much appreciated.
Thanks
Ryan
------------------------------
Director
Response Systems / Facet Consulting
------------------------------