You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I discovered the NR Observability maps, which make connections between different types of entities, not limited to services.
This is an option beyond NR service maps. But observability maps could be automatically plot, and automatically updated, like NR service maps.
Desired Behaviour
Using service maps, it is possible to automatically draw an architecture diagram of the different environments, the links between services, based on distributed tracing.
But we also know that NR service maps are limited in the entities that can be included in the architecture diagram, which is why observability maps exist.
Observability maps allow entities to be added to the diagram that goes beyond services. The problem with observability maps is that they do not allow automatic tracing, like services maps (with distributed tracing).
So by the end of this ticket, observability should allow for automatic tracing and updating of system architecture diagrams monitored by new relic, all this in real-time.
Additional context
It is important for us to have this possibility because we have a large infrastructure, and if we have a real-time diagram of all our systems, it will be easier to investigate where is the source of the problem when errors occured, and act in time to solve it.
The text was updated successfully, but these errors were encountered:
Summary
I discovered the NR Observability maps, which make connections between different types of entities, not limited to services.
This is an option beyond NR service maps. But observability maps could be automatically plot, and automatically updated, like NR service maps.
Desired Behaviour
Using service maps, it is possible to automatically draw an architecture diagram of the different environments, the links between services, based on distributed tracing.
But we also know that NR service maps are limited in the entities that can be included in the architecture diagram, which is why observability maps exist.
Observability maps allow entities to be added to the diagram that goes beyond services. The problem with observability maps is that they do not allow automatic tracing, like services maps (with distributed tracing).
So by the end of this ticket, observability should allow for automatic tracing and updating of system architecture diagrams monitored by new relic, all this in real-time.
Additional context
It is important for us to have this possibility because we have a large infrastructure, and if we have a real-time diagram of all our systems, it will be easier to investigate where is the source of the problem when errors occured, and act in time to solve it.
The text was updated successfully, but these errors were encountered: