Monitor
Monitoring is a rich space that includes centralized logging , telemetry, application performance monitoring, tracing, and more. Services usually integrate with these systems and stream data to them. These systems are used to diagnose any issues and trigger alerting systems when service-level objectives (SLO) are compromised.Monitoring 101
Reliability engineering practitioners use monitoring tools and techniques such as logging, application performance management (APM), request tracing, and more to maintain deep visibility into the health of their applications. Internal and external application communication must also be maintained. This is done via network engineering practices that include service discovery, load balancing, segmentation, and more. The goal is to ensure applications and infrastructure systems are healthy and performing within a service level objective (SLO), while providing observability tooling to diagnose issues as they arise.
Once a service is deployed to production we need to monitor it to know that our service is running and to ensure it persists in this state. The goal is twofold, it's once our application is in production we want to be alerted if something goes wrong such as a service outage where customers can't reach the service or when something bad is happening and it's impacting user facing services. The next thing is really realizing that at large enough scale any production system is a black box. We can't possibly understand how the whole thing works so what we really care about is whether we have enough observability - the ability to have enough probes and hooks into the service to understand what's gone wrong so when we get an alert we have enough of observability data to figure out what we need to do to remediate it and get the Service online again.
Applied monitoring in interdomain implementations
In distributed systems typical for interdomain workflows benefits can be obtained by coordinated monitoring efforts as solutions can be provided and redeployed over all endpoint instances while still maintaining their compartmentalization. Respond teams can act in the interest of the entire consortium and initiate first response triage as well as triggering affected members own response teams. Telemetry can be compared between members to identify misconfigurations or other performance affecting disturbances.
As complex as technical service monitoring can be we believe that the practice extends into business process and rule compliance. Monitoring changes in consortium member status to quickly revoke access or ensuring that the latest security patches are applied can make the difference between breaches and compliance.
API support channels
Ensure that your API stakeholders have a world class integration experience by collaborating with us! Supporting API users is a top tier technical task with high expectations separating it from the regular service desk experience, making it a perfect Sendex domain!
Boundary member life cycle management
Onboarding new boundary members as well as updating their creational status and terminating the from the network in a timely and secure manor is a process intensive and service centric task that we love to conduct and assist in!
Endpoint security management
We get it, managing sensitive data is a huge risk even without exposing it outside your own organization. A natural focal point for malicious activity targeting this data is your node why you should let us monitor and maintain your endpoints, either as a part of your current data centre or as a service.
Know your boundary members
Let us do the boundary member due diligence to ensure that each new member entering is the entity they claim to be ensuring that you know with certainty with whom you are communicating!