Importance of Operational Governance & Auditing 

ServiceBus360 has the inbuilt governance/auditing system that is capable of maintaining the logs of user activities in the resource properties under Operations. The audit log information will help the administrators to find out "Who did what" in the resource properties over a period of time. Consider a few example scenarios when the support user,

  1. Accidentally changes the status of a Queue
  2. Change the Auto Delete on Idle settings
  3. Accidentally enable Batched Operation

In these situations, if the user action is recorded and logged as an event, it will help the administrator to identify the root cause of the issue. Right now in Azure portal, none of the activities are audited. This leaves organizations to run their support purely based on trust, which may not be ideal in some mission critical situations like Healthcare, Financial services etc.

What are the sections that can be audited?

ServiceBus360's governance/auditing capability extends into the following areas:

  1. Operational History
    • Edited properties details in Queues, Topics, Subscription and Event Hubs
  2. Alert History
    • History of alerts and mail contents sent from ServiceBus360
  3. Activity History
    • History of Activities initiated, completed and failed in Queues, Topics and Event Hubs

Note: ServiceBus360 can only monitor and audit activities that user performs within ServiceBus360. It doesn't look for external sources. Ex., If a user has access to the Azure portal and active/disabled/send disabled/receive disabled a queue, then ServiceBus360 will not have any knowledge about the external changes.

By default, the audit history purge days is 7 days.

Audit Operational activities

Whenever the logged in user tries to edit a particular resource property and if the changes are successfully updated, an audit record will be created under the Operational History in Governance/Audit module of ServiceBus360. The audit information gets logged with the action that was performed on the property, the result of the activity, date time stamp when the operation was performed, details of the user who performed the action. Let's consider a scenario, Scott the logged in user edit's a Queue (Contoso) property such as the Queue Status and the Default Message Time To Live.

  1. You can use the Filter option to search the activities performed on a particular namespace, entity type, date and time to make the search easy
  2. Click the Refresh button to get the real time information
  3. Click the Information icon against the logged operation to view the reason for modification

Audit Alert history

ServiceBus360 alert history provides insight into recent alerts triggered in ServiceBus360, such as threshold alerts and health reports sent to configured channels in the account.  Each Audit Log entry lists the alert details, time of the alert, alarm name, channel name, transmitted status and the alert content.  For example, you could use the Audit Logs to identify when a specific threshold alert was triggered or to which notification channel the alert was triggered.

If you want to view all the records, leave the default value "All" in three filters. The From and To Filters shows the date and time, we can choose Date/Time until 7 days. After Applying the Filters, the screen will look like this:

When we click on the information icon, it shows detailed information about the Report like shown below:

Audit Activity history

Activities allow you to push sample messages into desired Queues and Topics. It can be used mainly for testing purposes. Ex: Sending 5000 sample messages into Queue or Topic with think time, batches, multiple threads etc. You can have multiple activities configured and executed them either instantaneously or via a schedule. These activities are logged in Activity history with activity details, entity path, activity status and list the complete properties of the activity.