Azure Services Operations
Do your support engineers create and delete distributed Azure Services resources like Queues, Topics, Relays, Event Hubs, Logic Apps and Functions with the Azure portal. Stop switching tabs to the Azure portal to create, delete and update properties of these entities. Your engineers can do all these CRUD operations in ServiceBus360 and all these user activities are tracked in Governance & Auditing section.
Import namespace entities from the XML file exported from Service Bus Explorer. Entities can be also imported from one namespace to the other, that are mapped in ServiceBus360. It is very helpful to easily migrate entities to Production from Dev and UAT namespaces after configuration and testing. It eliminates the need to manually create the entities in production namespace. The imported entities will also be reflected in the Azure portal.
In ServiceBus360, the messages can be received from queues and subscriptions. There are two techniques that can be used for receiving messages!
- Peek Look Mode
- Defer Mode
Defer and Resubmit Messages
When messages cannot be processed because of an error, the message is temporarily unavailable and becomes dead-lettered. Ultimately in critical scenarios, you want the message to be processed at a later time. With ServiceBus360, you can defer the dead letter messages to repair and resubmit the messages to the destination entity with ease.
Regenerate Message ID
ServiceBus360 allows you to regenerate/modify or edit a message ID when you try to resubmit a message to a ‘DuplicateDetection’ enabled Queue, this will help you to prevent the message from being lost. When you choose automated regeneration, the system will assign a new GUID as Message Ids. Alternately, you can edit to set custom message ids. for eg: invoice/201#/####.
Viewing the Message Details, properties, and the error
You can view the Message Details, properties and the error from the More Info icon. These separate grids will contain general information about the message properties, information about the error and the error description, and the associated messages that are referenced by the message id.
Rich filter option
When you have hundreds of messages retrieved from Dead letter, it will be easy to filter out the messages based on error reason. Say, if you want to filter the Dead Letter messages with error status as “Session id is null”, you can use this feature to filter the messages in the already retrieved result set.
Curious to send quick messages to test your integration scenario? You can send messages from the Queues/Topics dashboard with the inline option.
Do you send bulk messages manually in frequent time interval? With ServiceBus360 you can automate these tasks by configuring Activities (future and recurring). This Activities screen also displays the In progress, Configured Activities and also the History. You can edit the configuration of the saved Activities anytime.
As an administrator, you are bound to delete dead letter messages or messages for some obvious reasons on a periodic interval. This becomes a monotonous task on a daily routine, with ServiceBus360 you can purge messages in one go.
Azure Services Monitoring
Alarms act as a package for you to map required Azure Services Resources as a group and enable monitoring within the Composite Application. One of the most important features of ServiceBus360; it sets the base for the entire monitoring functionality.
Get notified whenever there is a threshold violation; customize when you want to receive the alerts – say, when there is a violation that exists beyond 10 minutes, or when things become normal, etc. You can also set how many times you want to be alerted if the violation persists. That’s not all – say, you don’t want to get disturbed with ServiceBus360 alerts on weekends, there’s an option to set this preference as well.
Health Check Notifications
As a support team person, you are forced to check the health of your Azure resources in your integration scenario every morning. Doesn’t this sound a repetitive task for you to perform on a daily basis? Don’t worry! With ServiceBus360, it’s easy to configure health check on the Azure Resources and receive automated emails with the health status at a set time of the day.
Wouldn’t it be nice for your administrators to sit in front of a big screen and view the status of all the monitors in one view rather than manually peek into the Azure portal for the violations? ServiceBus360 provides a full grid view that shows the bird’s eye view status of the configured alarms.
How many times in a day does your support person have to watch for ‘Trigger Runs Succeeded’ in a particular Logic App and take an appropriate action, or look out for ‘Total Billable Executions’? Wouldn’t it be nice if there was a way to set up monitoring on a set of metrics, get notified when the entity doesn’t perform based on Business SLA? Yes, that’s exactly what ServiceBus360 achieves through the concept of data monitoring.
Data Monitoring Dashboard
A vital part of Data Monitoring is how can you see the information executed by ServiceBus360. In data monitoring dashboard, the first thing you need to look at is the calendar view which will help you understand that on which days you faced problems. The chart area comes with different colour coding depending on the status of the Azure Logic Apps to easily distinguish the results.
ServiceBus360 allows you to set up API Monitoring and validate the actual response to the expected return. If there is a mismatch between actual and expected return values like codes or response data, alerts will be sent to the users with appropriate information.
Easily view the errors and warnings in the integration scenario within the application. Navigate to the problematic area with a single click! Keep track of the alerts that are triggered from ServiceBus360 through the Alert History feature.
Get notified of threshold violations from ServiceBus360 on one of the following notification channels – Email, SMTP, External Notification Channels like Slack, ServiceNow, PagerDuty, Microsoft Teams etc. All it takes is just a few minutes to configure these sources and receive the alerts.
Stop Alerts for Maintenance
At times, you may have to take the integration scenario down for maintenance – say, when you are integrating a new Azure Service or while making any configuration changes. In these situations, you can set ServiceBus360 to stop sending alerts during the maintenance window (to avoid receiving false alerts). Post completion of the maintenance window, ServiceBus360 will start triggering alerts normally.
User Access Policy
Do all your support personnel have the same access privileges to manage your Azure Service Bus? Are you unable to provide read-only access to a user or group of users to manage the namespaces in your Azure Service Bus? ServiceBus360 addresses your security problems by offering a user access policy mechanism where your administrators can set up user based (or) role-based authorization to your messaging system.
Governance and Auditing
Keep tracking the user activities on “Operations” tab of ServiceBus360. It’s as easy as seeing “Who did what Property changes on which metrics of which entity at what time”. The portal displays the alert history and alert mail sent for the recent 7 days.
There may be 100s and 1000s of messages passing through your Azure Service Bus entities on daily basis. ServiceBus360 Analytics data will be represented in three formats such as pie chart, line graph, and a simple grid view. Currently, the users can view the dead letter statistics for Queues based on various error reasons.