BizTalk360 CEO Saravana Kumar explains BizTalk360’s comprehensive BizTalk server administration and monitoring capabilities. He then moves onto explain Serverless360, A tool that will make monitoring and securing your integration resources much more efficient.
Integrate 2018, June 4-6, etc.venues, London
Now I’m going to introduce…in fact I probably got the easiest of all the introductions to all the speakers because I’m introducing the star of the show, and I’ve been told to say that because he’s my boss. All Saravana seems…needs to do is add the numbers 360 to end of any word, and it seems to become successful. So if Microsoft ever want to change the name to Microsoft360, I’m sure we can make it an even bigger success. So I’m going to present you the second best pool player in BizTalk360, the founder, the brains, and the driving force behind BizTalk360, ServiceBus360, Atomic Scope that seems to have missed the 360, and Document360, Saravana Kumar.
Saravana: Thanks, Duncan. By the way, I didn’t script what Duncan was talking, so it’s all his. Okay, I got 40 minutes now. So basically I split it into two different parts. The first 20 minutes I will concentrate on BizTalk360 and the second part we will discuss about the ServiceBus360. Even though, you know, like I’m guessing like…so how many of you are BizTalk customers here? Wow, okay. BizTalk360 customers? Great. Okay. So at the face of the product, the product might look similar and, you know, like it resembles the same but what we have done in the last few months, or last year is we had gone a bit deeper into the product, like every single feature got more additions, and it all coming from customer feedback. For example, to give you just an example, like, we have a BAM portal in BizTalk360 for a long time, but we have gone a bit deeper and brought things like related activities and a bunch of other features, which are much more enhanced. So I thought, you know, like I’m not going to spend too much time on the slides. I just, you know, like give an intro, very quick intro.
If somebody is fairly new to BizTalk360 and if they’re seeing for the first time just to get an understanding of, you know, what are the points we are trying to cover in BizTalk360. At the core of BizTalk360, the concept is basically you have developed something and then you’re taking it to production. And from that point onwards, it’s a big task to run it smoothly, you know, keep the operations guys happy. And, you know, like, how can you do it in a much, much more safer way? That’s the scope of BizTalk360. So we never deviated from that vision right from day one. It’s 6 years and we have released over 50 releases in the last 6 years. So every three months, once, there was a consistent release of the product, and we bundled in at least two to three new features into the product. It’s mainly driven by our own experience working with the industry and a lot of our partners and customers. And we got a feedback portal which is very popular, and we get a lot of requests through that portal as well.
So the number one goal is, you know, like, the support side and they…you know, the security is one of the biggest aspect. So a lot of times, you know, like the BizTalk admin console got its own limitations, like, in the sense it’s designed more for a hardcore BizTalk guy. And when it comes to operations, you know, sometimes people struggle especially from the security side of things, it’s all or nothing. And that’s one of the things we address.
The second big picture is actually on the monitoring side, you know, like people use different techniques for monitoring. So typically they use something like SCOM. We also keep hearing, you know, like when we are in some of the sales calls, we do hear things like, you know, we try to use Nagios or SolarWinds, etc. But what typically happens is, it’s so easy from a very top level to say, we do cover BizTalk monitoring, but once you go a bit deeper then, you know, like, it just comes down to, “Okay, we do monitor some server CPUs, and disks, and event logs, and stuff like that.” But people coming from a BizTalk background, you know, like it’s much more than that. And I’ll quickly cover some of that on the demo, like, what we do.
And analytics is another big area like, you know, for most of the team like BizTalk is such a big black box. You really don’t know what’s going on, unless otherwise, you build some custom solutions on top of it, either using BAM or some kind of a custom tracking solutions to get some data out of it. So we wanted to productize it as much as possible, and actually that comes as part of the analytics.
So as I said, you know, I don’t want to go into the slides, let me quickly switch over to the product itself. Okay, so this is what BizTalk360 is. To start off, you can see it’s a pretty modern web interface, and it’s people coming from the BizTalk admin background side of things can appreciate, you know, the what level of…the user experience you’re seeing here. So this dashboard is not a static dashboard, it’s a fully customizable dashboard. So you can go on to add widgets to this dashboard. So when I said in the beginning like we are investing to go a bit deeper, so some of these examples are, you know, classic ones. For example, we added lot of useful widgets to the product as well. So the EDA, if you’re dealing with a lot of EDA stuff, we brought some lot of EDA related stuff, and if you’re working with the ESB toolkit, exception management, those kind of things. So we brought a bunch of ESB related widgets.
So it’s fairly easy to, you know, like, add and remove whatever you want. So it all adds to the bottom of the widget of the dashboard. And you can go and, you know, these are some of the stuff I just added. So out of the box we provide quite a bit of useful widgets. So things like for example, you know, when…again, it’s the same story of going deeper. So we brought this widget called a BizTalk server license, because we figured out, you know, like one of the top most article on our blog is our licensing document. You know, like, how do you license your BizTalk environment? People are not aware like how much license you need for your production system, how does this whole… They made a big switch in 2013 how you license your BizTalk environment. They moved from CPU to core and people got a lot of trouble understanding that.
So we got a widget which quickly tells you exactly, you know, like, how many licenses do you need for your BizTalk environment? So there’s quite a bit of logic behind the scene to bring it on. So this widget itself, you know, you can easily…you know, you can customize it, you can say…you know, you can move it around, or if you don’t want something, you can close it, you can customize it, and we also support multiple sizes, and things like that.
A lot of our customers got very nice dashboards built for different environments. And you can also have multiple dashboards as well. It’s not just one dashboard, you can have multiple of them to cover multiple things. So some people might have…this is the SAP to Oracle Integration as part of that you want a bunch of items in it, you can do it pretty quickly.
The second biggest value proposition what you get from BizTalk360 is actually a consolidation of a lot of your tools. Right now, if you look at how you operate your BizTalk environment, so you’re looking somewhere around, you know, six to eight different tools to run it. So BizTalk admin console, of course, is the obvious one. So in addition, you might be using, BAM portal, ESB portal, the SQL Server Management Studio to do some SQL stuff. If you’re using some monitoring tools you might have, like, SCOM interface, and things like that. In addition to that, you know, the event viewer is very important in a BizTalk world and that’s where you go and figure out all the failed…anything goes wrong in BizTalk, your first point of contact will be admin console, and the second point will be event viewer. So those kind of…you know, we brought all those things into the product basically.
So you can see like the ESB portal, you can see the ESB exception data right in the BizTalk360 console. So it’s basically, you know, like we rebuilt everything from scratch. It’s not like, you know, we resurfaced everything on what’s on the standard portal, so it’s been built and developed, and it’s also improved significantly as well. So, we have things like for example, you know, like this is a small knowledge base article here, you can view the…you know, like, there is somebody has returned some kind of a knowledge resolution for that exception. You can maintain this knowledge base completely. And you can attach this knowledge base to multiple places, like, you know, some specific events happening in your system, some suspended instances happening continuously, you can attach all those kind of things.
So we have ESB portal, and when you go to data access you can see you can have a BAM portal, even you can access the SQL server from here. There’s a bunch of queries you can store and execute. You can access the entire event viewer across all your BizTalk and SQL servers from single place. You can query your message box. You can query your tracking data. So everything, you know, basically, it’s a single tool for you to, you know, like quickly, you know, visualize and see what’s happening in your environment. Okay, there is a graphical flow, which shows, okay, there is a error in the system.
And you might also notice we have like this Azure services. So this is also something we added, because what we’re noticing right now is people are moving more and more towards the hybrid model. So you have on-premise BizTalk, you have a lot of things happening. But at the same time, you know, you’re investing, started investing some of your new flows in Azure, maybe you’re building some Logic Apps, so your team is using a integration account. So you don’t want…again, we are going in the same theme of, you know, reducing the number of tools you need to use.
So you don’t want to use BizTalk admin console and on-site, and Azure portal on the other side. So you can quickly go and say, like, you know, what are my Logic Apps? You can associate subscriptions to a specific environment so you might have a production subscription or a UAT subscription once you attach it. So you can actually view all those Logic Apps. And you can see those, you know, the health of those Logic Apps. So, you know, what’s running, what is the, you know, the triggers, and actions, and tracking, and everything all comes into BizTalk360. So, there’s basically, you know, like…so it’s just reducing the number of items.
So the other major area is the security is one aspect. So, you know, okay, you can see the product is getting more and more powerful. So you of course, you don’t want to give these assets to all of your people, so you wanted to control it. So that’s a challenge what you see in BizTalk admin console. So once you give people access to the admin console, they’re going to see pretty much everything. So here, you know, you can go to settings and then we have a user access policy. So under user access policy, you can define a policy for example, if I look at Claire, if I go edit it, so you can say this is the standard AD domain user. And then you can go to different applications and you can provide the access for applications you wanted to give access to Claire.
And it can go very granular. And say like, you know, you don’t want to have Claire access for the message content and context, if you don’t want to give access to things like…if you want to give read-only access, it’s a very good use case. Because you have a production system and you need developers help to go and fix some things but you don’t want them to really, you know, like have superior rights on your production environment. So in that case you can give complete read-only access to it.
So I think that’s, you know, the operations and support side of the story, I think you got the idea. So it’s basically, you know, like, six years of investment and making it better and better. So, if you are using BizTalk, you know, it’s a kind of a no-brainer for you to take a look into the value what we can bring from BizTalk360.
So the next big thing I wanted to cover is the monitoring, because of course, you know, you invested quite heavily on BizTalk and it’s important to make sure it’s running smoothly. So we have this concept of alarms you can quickly, you know, very quickly create an alarm. So this is just our test environment. If you look some of our customers’ production environment, they have like really…some of them got hundreds of alarms. So every single interface or, you know, like a integration scenario you can have, you can actually have alarm for it.
So in this case, for example, I can quickly say this is…I want to create a threshold based alarm and we’ve got different notification channels. Let’s say it’s, you know, like Oracle to SAP integration. And I can say I will put my email ID where I want to get notified. And we all got some advanced things like templates and stuff like that. So I’ll leave all those things. And you say it’s a threshold based alarm. And I wanted to get notified every…you know, if the violation passes for one minute I wanted to get notified. In some cases you only wanted to get notified during business hours, you can also restrict it if you want to do that, if you don’t want to get alarmed in the middle of the night.
So once the alarm is created, it’s a very abstract concept so, you know, like okay, Oracle to SAP integration. And after that I can simply go to different artifacts I can monitor. So for example, I can go to applications so that should list out all the applications. And I can pick up, you know, some stuff and say like…so I wanted to monitor the FTP receive location, or I don’t know whether you got anything here, this is standard.
Okay, so I can say I wanted to monitor this and say, you know, I expected state is to start. And we also have like a really interesting feature called Auto Correct. So a lot of times, you know, for example, if you’re using FTP receive location, it can go down for any number of reasons, it could be network connectivity issue or, you know, there’s something wrong on the other side. It’s more of a momentary problem rather than a permanent issue. So in that case, you know, you can pick it up and say, like, “I wanted to enable auto correct.” So in that case, if something goes wrong, it will automatically bring the receive port or a send port back into action. So there are, like, we got a very good coverage of things what you can cover, a similar way we cover your services as well. So as part of the Oracle to SAP integration, you might have couple of Logic Apps or a couple of APA apps in part of those solution, you can actually monitor that as well.
When it comes to BizTalk environment, you know, you can do the standard stuff like host instances, web endpoints, and database queries, and BizTalk Health Monitor or MBV what we used to call it. So this is where, you know, I wanted to differentiate. You know, anybody can climb the cover monitoring for BizTalk, but you can see the depth to which you can go when it comes to monitoring.
I just want to highlight this one important thing, Host Throttling. This is something very, very critical, because a lot of times, your BizTalk can go into some, kind of, throttling state. Few releases back, we reintroduced a throttling analyzer, which will give you like a very good visualization of whether your environment is working correctly or under some, kind of, throttling condition. So recently, we brought this capability called throttling monitoring. So you can actually go and say, you know, I wanted to set up a monitor alert whenever the system goes into throttling condition. And it’s quite, you know, advanced in the sense like, you can go any throttling, or you can specify interested in rate throttling, or a database size throttling, and things like that. You can go much more granular and you can control it.
So this in itself is a huge time saver because typically what happens is, you know, your system is under some, kind of, a throttling condition and you asked your BizTalk admin guy or somebody in charge of BizTalk to go diagnose the problem. And trust me, it will take a day at least for them to understand whether there is a throttling condition or not. So this is all there, you know, just a few clicks here and there and you got complete throttling within few seconds basically.
We got file locations, you know, maybe you’re watching, still you’re using the file based integration. So you may want to keep the growth of that folder, like whether there are too many files accumulating in that folder, you wanted to monitor that, you can do that. And the same can be done for FTP and SFTP locations as well. If something is piling up on that side, you can get notified. So cues is interesting, you know, like we cover three different types of cues, the Standard Windows MSMQ, IBMMQ is very popular like a lot of people with HIS and host integration, you got IBM cues involved in your integration. You can monitor things like the depth of the cues and a bunch of other properties.
And also, we spent a lot of time on the user experience side because we wanted to make it seamless. So you can see a lot of those configurations are pre-populated. Basically what we do is, we go through your environment and we figure out whether you will have any of the ports configured for your IBMMQ, and then we pick up most of the configuration, and it just in a couple of clicks here and there, and you will get that complete monitoring in place. So that’s one side of the story.
And we also have something called, you know, data monitoring. So, which is, you know, like viewing the historical data. So the use case here is, say, for example, you got some kind of a SLA ,so process, you know, like a 20 purchase orders every hour coming from SAP system. You can quickly create a data monitor…you know, to create an alarm with that data monitoring stuff, and you quickly say, you know, like, you’re looking for some, you know, messages and whether you’re getting like, that volume of messages going through the system. If not, you know, you just get notified. So that’s on the monitoring side and, you know, probably I’ll just spend a minute on analytics.
So the analytics is pretty similar. So we provide a lot of analytics data on top of it. So you can have like a similar kind of widget concepts but here it’s more about the runtime metrics, like, you know, transmission failures, and message performance, and those kind of things. You can also have reporting as well. So you can quickly, you know, like you produce this kind of report very quickly. So this is all coming from your analytics data. And all these things without you writing any code basically, you know, you just install 360 and leave it running, and you start getting this kind of reports and you can download it as a PDF. And it’s quite a bit of value what you get out of your…because every one of us, you know, like BizTalk enterprise is not cheap you’re looking at least, you know, $100,000 investment. And you get all these things out of the box for that kind of investment.
So messaging patterns, we identify different patterns in your system, so we provide this kind of what are the different patterns of messages that’s going through your system. So again, same concept we explore whatever it’s in your database and we just bring it on basically. Okay? Okay, I think that would have given you like a very quick intro, I want to stop there from a BizTalk360 perspective. I’m sure like, a lot of you might have seen most of the stuff, there could be a very good 20 minutes recap for you to understand what we have done. For some of you new, like, it would have been an opportunity for seed. If you’re interested, you know, we’re outside, please come and talk to us. We can probably, you know, do a much more deeper demo.
Okay, so with this, I would like to switch to ServiceBus360. ServiceBus360, we started the project something like 18 months ago, something like that. So initially we started off as a concept similar to what we had done for BizTalk and BizTalk360. We felt it’s a similar need as required for Service Bus, because the messaging from people coming from an integration world, messaging is the key. And if you look at the current scenario now, Service Bus is the messaging platform, what you have. You know, like, you really don’t have much option like, you know, if you’re into messaging, you know, Service Bus is the option for you to look into. So we thought…we saw there’s a lot of gaps in terms of, you know, from an operations and, you know, like managing it.
So, the Azure portal is, kind of, limited in terms of what you can do with Service Bus. So, how many of you are using Service Bus explorer here, right? Okay, Service Bus Explorer is a great tool, and Pablo was trying to address that gap. And of course, you know, Pablo is a full time employee with Microsoft, I don’t even know whether he’s still working with Service Bus. I think he moved on and, you know, like it’s a, kind of, open-source product. So that’s something we wanted to address that gap, and it’s more than what Service Bus…just give it as a context as an example, like, why we are looking into addressing that gap.
So in a similar way we wanted to provide, you know, like one platform in operations monitoring and analytics for Service Bus. So now I think today is a important day for us, we are repositioning that product in a different way. I’ll go through the slides quickly in terms of, you know, like how the product initial concept started and where we are heading with that product in the future direction.
So you’ve been hearing lot of talks for the last day and all, from Microsoft, and we are all fully aware of, you know, like the new buzzword coming like, you know, serverless and everything. Like, you don’t need to worry about infrastructure. I don’t need to explain this description but just on a very high level, the serverless, the term basically means. You don’t need to worry about your infrastructure, or servers, or, you know, things like disks, and CPUs, and stuff like that. So you only worry about things which are, you know, you work on the platforms and you don’t need to worry about the scale. If you get…you know, today you’re processing 100 messages per minute, but in the future, if you wanted to process 5000 messages per minute, you don’t worry about the infrastructure, it will scale automatically. And also, you don’t do upfront investment, you pay per use. So you might start small and as you grow and as your solutions get bigger and complex, you pay according to your requirements basically, right?
So these are, you know, some of the technologies what comes under the serverless, focused purely on integration background, basically, right? So now we are pretty much familiar with all these concepts now because people like, you know, Dan, and John, Fancy, and Kevin, they’ve been talking on each one of these individual technologies. Like, you know, Jeff spoke about functions, and John on Logic Apps, and Dan on Event Grid, and we all understand, you know, the usage of serverless.
Most of this, you know, like, if you look at how you use these technologies, basically, most of this serverless technologies on silos, when you look at it as independent items, it got very less value, right? Because if you want to make sense out of Event Grid, you need something on both sides, right? So you need events from, for example, from a storage, and that raises the event, it goes to the Event Grid. And then you call a web book or another Logic App, or something like that. Same for Logic Apps as well, okay, the Logic App on its own, it’s not going to do much, you need to put some connectors, and you need to talk to things on both sides to make any sense out of it.
So this is all…as I mentioned, it’s not going to add too much value on silos but when you start putting things together like this, that’s when you really realize the power of this technologies together, right? So these are some of the idea… I just did a quick search on a search engine, and then these are some of the majors I got right out of a standard search engine. So these are the type of things what people are building now, right? Okay, you got something coming to Event grid, and it spans out into Logic App functions, and web books, and things like that.
And this is something what people started to call it as serverless apps, right? So this is how it’s all looking. So I’m going to ask a question like, how are we going to manage this? What options do we have? So, okay, I’ll rephrase it another way. How many of you are confident you can give Azure portal access to your support people? Okay, so that’s the problem. That’s the USP we wanted to address, because we run off some of our products on Azure and we are not confident giving access to our own support people.
You got fantastic role-based access and everything in Azure Portal, but how many of us are willing to, you know, go spend some time and set some permissions, and access, and how are you going to do that? Again, if you log in to Azure portal now, all you will do is like things hanging all over the place, right? Okay all resources here and there, and you’re never going to get the visibility of this, kind of, you know, “This is my app.” So you’re not going to get, you know, that no application visibility. Okay, this is my simple serverless app, but I don’t have the visibility how I am going to manage it. And also I mentioned that Service Bus explorer example, some of the tooling are really, you know, like premature, like, when you look at real production systems and you wanted to do something really concrete, the tooling lags significantly in Azure portal.
I can see as a company, as a Microsoft, you know, it’s very difficult for them because they need to set their boundaries. Otherwise, when you have, you know, like 100,000 people and 100 different services, when everybody starts spinning their own portals, it becomes completely non-manageable so they can’t do it. In fact they’re dated, if you look at the original version few years ago, they used to have a portal for SQL server and they had a portal for BizTalk services, and they killed everything. And they said there’s only one portal, Azure portal. And they wanted to bring everything into that portal. And that brings the level of concern for the product groups as well because they can only work within the boundaries of that portal and that brings the tooling limitation. No consolidated monitoring as well. Okay, Azure portal got a good monitoring story that you can do a lot of metrics. But again, it comes back to the same problem of they are siloed, right? Okay. If a single Logic Apps, you know, if it’s failing or doing something, okay, it’s important to monitor that but it makes more sense to understand the context in which that Logic App is actually running. So that’s the problem we wanted to address, and again, the security as well.
So what we had done in the initial days is as I said, we started this product as a more focus as advanced to tooling for Service Bus, but now based on feedback and our own experience, we are actually going to rebrand this product into Serverless360. Okay, let me quickly go through what it actually means. So first, the foremost is managing serverless application. So as I mentioned, so what you can do is you can actually start grouping those entities which are relevant to your application. So it could be…you know, in this case, you have an order processing app that got for example, you know, two cues, two functions, two Logic Apps, some APIs, all put together as a serverless app, and you can say this is basically your order processing application. And that entity is going to can actually come from different subscriptions, different resource group, as long as you connect your service principles, we can pull all those information and you can start constructing this serverless applications basically. And once it’s there, you manage it…from that point onwards, you start managing as more like as single applications, you’re not working with independent entities, but you’re working at a reasonable application level.
So we wanted to also provide deep tooling. So, you know, like complete CRUD operations on all those entities, user [SP] ability to resubmit, repair, and edit, and resubmit messages. We identified things like if you have a duplicate detection enabled on a cue and if you resubmit a message, you need to change the message ID of that message, so those kinds of things. If you don’t have this functionality, your developer is going to write a console app to do that, right? So that’s a problem we wanted to address.
And we also have some scheduled activities. Probably, you may have wanted to purge all those dead letters every day or something like that, right? So those kind of deep tooling is what we wanted to bring into the context of serverless apps. So this is, more it’s, right now that the deep tooling is what we have for cues and topics, but in the future, you know, we have roadmaps to cover deep tooling for all those serverless apps related entities. And you also can monitor those as a single entity. Okay, I am interested in what happened to my order processing app, I’m not really interested in what happened to this independent function or a Logic App, or a cue, or something like that. So you manage it at an application level.
Security and governance, again, so this is addressing the original problem I raised because right now, everybody is a bit skeptical giving access for the Azure portal. So here, you give access to a serverless app and they can only see things which are inside that serverless app. And we also address the standard auditing functions like, you know, if somebody’s making property changes or somebody resubmitting messages, all those things are all part of the application.
So we originally started this ServiceBus360 as a complete source-based application. So we run the whole thing like how Azure is running most of the serverless things. But we hit a bottleneck, like a lot of our, you know, like government customers and healthcare customers, they’re not confident to give their connection details to a third party app like us. So based on the feedback, we now have a full private hosting option. So you can actually take this and host it on your own infrastructure. So you run it in a similar way how you can take BizTalk360 and install it on your own environment where we don’t have any access to it. In a similar way you can you can run the entire Servelessapp360 in your own data center or in your own virtual machines.
So I think I’ll quickly go through a demo, you know, I want to show it’s all real, it’s not just PowerPoint. Okay, so this is how the application looks. So you can see here you have two choices, either you can manage individual stacks, so when you want to have some kind of a deep tooling for your cues, and topics, and things like that, you can go and navigate via this, or you can go via this composite application root. So you can see we have bunch of applications already configured. You know, this is one of our production environments, couple of production environments that got some entities. And let’s take this example of, you know, this order processing application.
So you can see this particular app got a bunch of cues, topics, and some Logic Apps. For some reason I think they are disabled and it’s not in a healthy state. And that could be, you know, part of your monitoring to get it done. So I can go to, you know, topics and then I can say like…you know, I can see the subscriptions under this topic. I can also say like, you know, I wanted to maybe send some sample messages to this topic. And by the way, it’s all controllable. You probably don’t need to give send messages option to everybody in the team, so you can actually change the user access policy so they don’t get access to these Send Message capabilities.
So here let me say I’m throwing some five, six messages, you send a message. And it’s all, you know, like get transmitted, so you get a very rich tooling for your day-to-day operations. Okay, my mouse. Okay, so it’s there and I can go to, you know, open up and see one of the topics, and I can see if there’s anything, you know, like dead letter messages. So, that could be, you know, for the demo purpose we put some messages in a dead letter. So the network…okay, and then you can basically, you know, choose what are the messages and you probably want to, you know, like resubmit the message. And you can choose to which cue or which topic you wanted to resubmit that message.
Let’s say I’m picking up this duplicate message thing. So here, you know, this is the original message ID but you may want to change it to something like, you know, like order/2000/18, or something like that, and you can resubmit it back. So, also, you know, maybe you can do multiple…maybe there are, really sometimes, you know, hundreds of messages we wanted to resubmit, you can go to Resubmit, same, same concept but this time, you know, I can’t go and type each one of them say, okay, maybe generate unique message IDs so that you can resubmit it back.
So it’s all again coming from our own experience of, you know, like practically what are the things you will see on a day-to-day basis, and that’s how we basically build the product. So activities, you know, as I mentioned, you know, there may be a set bunch of things. Maybe you wanted to purge the dead letters on a daily basis, so you can, you know, quickly see how it’s been configured. You can do some of the activities regularly, like, you know, resubmitting messages, resubmitting and delete, or you can simply delete the messages, you can schedule it how you want to run it every day, or every other day, or, you know, every Monday or something like that. And then, you know, once you save it, the system background jobs runs and cleans up everything.
So monitoring, you know, we have really good use cases like…I have only a couple of minutes, so I’ll quickly show the important one. So we have this, you know, historical data monitoring stuff. So maybe you may want it to monitor your increase rate at which the messages are coming into your system and there may be some SLS, so you can easily configure it.
If I look at one of those failed ones, you can see that a lot of conditions I wanted to satisfy in that particular cue or topic, so, if it’s not matching any of these things, you know, the action failed item is greater than 10, alert somebody. You know, the runs completed is, you know, less than one, you alert somebody. So you get, you know, like a quite deep tooling basically, in terms of monitoring.
So in terms of, you know, composite apps, you know, like, you can easily add stuff to the app, you know, you all you say is, you know, associate resources. So in the setting side, you go and, you know, associate some of your subscriptions and we pull all those things, whatever available in those subscriptions and you pick and choose, you know, these are the things which comes as part of my, you know, serverless app and then you can manage it as a single entity.
We have our ServiceBus360 team here, so Aaron who is sitting in the front is in charge of the Service Bus team. So if you wanted to get more info, you know, please feel free to come and talk to us. Thank you very much.
Fill the form below to get all the presentations delivered as a single zip file in your mailbox.
byJon Fancey & Matt Farmer
byMicrosoft Integration Team