Yes indeed - this is a common use case, but your phrasing leads to more questions...
Will the CUSTOMERS be using Instana and you want to segregate THEIR usage?
If so, you likely will want to consider separate Instana environments for each customer.
Instana agents can report to multiple backends. One such arrangement is to have all customer agents reporting to both a dedicated backend (for the customer) and a general backend (for your management of all customers)
If you are managing multiple customers and want to distinguish and manage them separately from others, that is definitely doable.
Presumably, there are distinguishing characteristics for each customer - portions of URLs, hostnames or tags, namespaces.
It is a core feature of Instana to create filters and Application Perspectives for just this sort of segregation in the UI.
A saved filter will allow selective infrastructure to be viewed.
Application Perspectives can be created that focus on a specific customer.
Once those are created, events and analytics can leverage the same filters.
Feel free to elaborate or add detail if this is not clear
Regards,
John Wikoff
Instana Technical Value Advisor
------------------------------
John Wikoff
------------------------------
Original Message:
Sent: Wed March 22, 2023 10:06 AM
From: Carla Raffi
Subject: Instana multi tenancy / multiple monitoring environment
We should possibly integrate different customer environments into a single on premis Instana installation
Is it possible if the different customers have the same ip addresses?
Is it possible to keep them in separate enviroments and which is the best way to implement it?
------------------------------
Carla Raffi
System programmer
Sogei
roma
(39065) 025-2866
------------------------------