GISBlis Observability for ArcGIS
Know before your users call: every map service, end to end.
We turn the logs, metrics and audit trail that ArcGIS Enterprise already produces into service-level dashboards, alerts and security detections in Elastic. We can set it up for you or run it for you.
Is this you?
Users notice before IT does
- 01
Do your users notice a slow or failing map service before IT does?
- 02
Does root cause take hours because monitoring sits in a GIS-only silo?
- 03
Can you show an SLO for the availability and performance of every map service?
For organisations that run ArcGIS Enterprise themselves (on-prem, Azure/AWS or Kubernetes) and depend on GIS operationally.
- Safety regions
- Water utilities
- Municipalities
- Provinces
- Infrastructure operators
- Network operators
What you get
One view of your ArcGIS Enterprise
- 01
See per map service what is slow and why
SLOs and burn-rate alerts per critical service, plus synthetic checks on REST and tile endpoints.
- 02
Find root cause faster
Server, Portal and Data Store logs, the metrics API, IIS/Tomcat and the geodatabase sit in one timeline, correlated by request ID.
- 03
Prove upgrades worked
Before/after performance baselines and an upgrade-readiness report.
- 04
Hold every map service to an SLO
Availability and performance targets per critical service, tracked over time and visible to the business.
- 05
Size capacity on facts
ArcSOC instances, cores and wait times, instead of guessing.
How it compares
Alongside ArcGIS Monitor, not instead of it
| Capability | EsriArcGIS Monitor | BlisObservability for ArcGIS |
|---|---|---|
| Esri-native GIS depth and relationship graphs | Esri · ArcGIS Monitorcovered: Built by Esri for ArcGIS | Blis · Observability for ArcGISpartly covered: Links each service to web tier, servers and geodatabase |
| GIS usage analytics | Esri · ArcGIS Monitorcovered: Core strength | Blis · Observability for ArcGISpartly covered: Portal usage dashboard |
| Correlation with web tier, OS, database and SIEM | Esri · ArcGIS Monitornot covered: GIS-only view | Blis · Observability for ArcGIScovered: One timeline, correlated by request ID |
| SLOs and burn-rate alerts per map service | Esri · ArcGIS Monitornot covered: Not covered | Blis · Observability for ArcGIScovered: SLO templates and about 15 alert rules |
| Security detections and audit logs | Esri · ArcGIS Monitornot covered: Not covered | Blis · Observability for ArcGIScovered: Detections for admin activity and permission changes |
| NIS2 / Cbw evidence dashboard | Esri · ArcGIS Monitornot covered: Not covered | Blis · Observability for ArcGIScovered: Logging-coverage dashboard |
| Licence model | Esri · ArcGIS Monitorpartly covered: Separate GIS-only licence | Blis · Observability for ArcGIScovered: No extra GIS-only licence; customer-owned Elastic subscription |
What is in the pack
From collection to runbooks
- Collection
- Elastic Agent/EDOT on Server, Portal, Data Store and Web Adaptor hosts. Sources are the 12.x Prometheus metrics API (log-based metrics on older versions), 11.4+ JSON audit logs, IIS/Tomcat logs, host and geodatabase metrics (SQL Server, PostgreSQL, Oracle) and Kubernetes metrics.
- Synthetics
- HTTP and browser checks on critical viewers, REST, feature and tile endpoints and Portal sign-in.
- Data model
- Ingest pipelines to ECS plus arcgis.* fields.
- Dashboards (6)
- Executive health · Service performance · Server/ArcSOC capacity · Portal usage · Data Store/geodatabase · Security and audit.
- SLOs and alerts
- Availability and latency SLO templates, plus about 15 alert rules (service down, latency burn, ArcSOC saturation, certificate expiry, failed logins).
- Security content
- Detections for anomalous admin logins, new SOE/extension installs, sharing and permission changes, privileged-account creation and web shells under ArcSOC.exe.
- Integrated AI and AI agents
- The Elastic AI Assistant and AI agents sit on top of your ArcGIS data, so your team can find root cause and ask questions in plain language.
- Knowledge and packaging
- Runbooks per alert, onboarding guide, data-flow description for a DPIA, Git repo with versioned releases, automated deployment.
Supported
ArcGIS Enterprise 10.9.1 to 12.x (full pack from 11.4; older versions get a log-based pack as upgrade bridge) and ArcGIS on Kubernetes. ArcGIS Online is limited to synthetics and the usage API.
Deployment
- A) Elastic Cloud EU, customer-owned (default)
- B) The customer's existing Elastic
- C) Self-managed / sovereign
The offering
Scan, Assess, Implement, Run
Click a step to see what's included
01Scan · free · 1 h
Find your blind spots before your users do.
You spend one hour with one of our Elastic engineers. Together we map how your system is built, which logs and metrics it already produces, and where you can't see problems coming.
Book your free scanWhat we do
- Go through your architecture, versions and current monitoring tools
- Talk about what goes wrong today and how you find out about it
- Check upcoming upgrades, audits and NIS2 requirements
What you get
- A two-page blind-spot overview within 3 business days
- Your three biggest monitoring gaps
- A proposal for an Assess, if it makes sense for you
What we need from you
- Someone who knows the system, and one hour of their time, online or on site
Good to know: It costs nothing and you don't commit to anything.
02Assess · 2 weeks
Proof on your own data, before you commit.
For about two weeks we measure your real environment. We connect a temporary Elastic project read-only and nothing changes in production. Then we design the observability pack that fits your environment.
Plan an AssessWhat we do
- Agree with you which critical services are in scope
- Collect logs and metrics and set a baseline for each service
- Analyse the data for blind spots, upgrade readiness and logging coverage
- Design the pack and size the Implement (S, M or L)
What you get
- A baseline report with at least 10 prioritised findings
- A performance baseline for each critical service
- An upgrade-readiness check and a NIS2 logging-coverage check
- A pack design with a fixed Implement quote
- A management presentation of the results
What we need from you
- A named application lead and an IT-ops contact
- Read access to the admin API and the log directories
- Your list of critical services
Good to know: The price and scope are fixed. Part of the Assess fee is credited if you order Implement within three months. The Assess is finished once we have presented the report to you.
03Implement · fixed price · S/M/L
Production-ready observability, in the size that fits.
We roll out the pack across all the environments in scope: dashboards, service levels, alerts and checks, all set up for your system. Because the pack is a product and not built from scratch, you get a fixed price and a short lead time.
Request a quoteWhat we do
- Install the agents and data pipelines on every in-scope host
- Deploy the ready-made dashboards and set up SLOs for your critical services
- Send alerts to one channel of your choice: ITSM, Teams or e-mail
- Set up synthetic checks that test your services the way a user would
- Write runbooks and train your team
What you get
- Dashboards and alerts that are live and already filled with your data
- An SLO and a synthetic check for every critical service
- Runbooks, a handover document and a data-flow description (useful for your DPIA)
- Two half-day training sessions
- A joint acceptance test
What we need from you
- A host or Kubernetes namespace for the agent, plus change windows
- An alert channel and people to run the acceptance test
Good to know: You choose where it runs: Elastic Cloud EU, your existing Elastic, or self-managed / ECK. Optional extras are security content (detection rules and NIS2 evidence) and a self-managed platform build. Typical lead time is 3–8 weeks. After Implement you can move on to Run or hand everything over to your own team.
04Run · managed · monthly
We keep it working and keep improving it.
Observability only pays off if it keeps up with your environment. We maintain the pack, tune the alerts and report to you every month, so the dashboards stay accurate after every upgrade or change.
Talk to us about RunWhat we do
- Maintain the pack and agents
- Update the content within 30 days of new application or Elastic releases
- Tune the alerts so they stay useful and don't turn into noise
- Triage alerts during service hours and escalate to your team (Standard)
What you get
- A monthly service report by the 5th business day
- A quarterly review of your SLOs and capacity (Standard)
- One upgrade baseline per year (Standard)
- Change hours included every month (Standard)
- Agreed response times and a clear escalation path
Service levels
Essential
maintenance, content updates, quarterly alert tuning and a monthly report
Standardrecommended
everything in Essential, plus continuous tuning, alert triage, a quarterly review, an upgrade baseline and change hours
Good to know: Service hours are Mon–Fri, 08:00–18:00 CET, and 24/7 cover is available on request. Contracts run for at least 12 months and renew each year. Add-ons are security monitoring and extra environments. We restore your observability; we do not fix incidents in the application itself.
Ask us for a quote after your scan.
Next to regular monitoring
Why add it to what you already have
- A host being up does not mean the service is healthy: you get per-service latency and root cause
- It adds a correlation and security layer on top of your current tools; the GIS team keeps theirs
- ArcGIS Monitor can stay in place for GIS admins
- One timeline across ArcGIS, web tier, OS and database instead of separate silos
Why Blis
Built for ArcGIS, owned by you
- No other Elastic partner or APM vendor offers ArcGIS-specific content
- Built on Esri's own 12.x metrics API and 11.4+ audit logs
- The customer owns the Elastic subscription and gets the content handed over, so there is no lock-in
- Blis Digital is an Elastic Select Partner
ArcGIS · use case
Map services that stay fast
Set an SLO for each critical map and feature service and get alerted when latency or availability starts burning budget. Logs and metrics from Server, Portal, web adaptors and the geodatabase sit in one view. You see the root cause in minutes, with a runbook attached, before users call the GIS desk.
Step 1 is free
Start with a scan of your ArcGIS environment.
Contact