aloha and thank you for joining us my name is brian hollandsworth from our itsm team and joining me today is colin o'brien from our devops team today we're going to provide an overview of the now platform and show how gremlin can be used together with servicenow itsm and devops to get started i want to share how servicenow connects people functions and systems together using our cloud platform the middle portion of this diagram contains many powerful capabilities that serve as the platform's foundation the workflow engine connects internal functions and seamlessly integrates with external systems using integration hub our native machine learning ai and analytics capabilities provide automation and insights without requiring external providers to let people choose how they want to engage with servicenow we have persona based experiences on web mobile and conversational interfaces and we also have api access to keep everyone on the same page our configuration repository uses a common data model that is shared across all apps and finally we include a set of no code and low code to dev tools for anyone who wants to build custom apps on the platform we've used this platform to create industry-leading products for it employees customer service and custom app development within it workflows we offer several product lines to manage a service throughout its lifecycle there's not enough time to go through all these today so i encourage you to visit our website to learn more earlier this year we partnered with gremlin to make it easier for customers to use our products together to do this we built an integration hub spoke with the actions listed these can be ran manually using a catalog item request or incorporated into flows that run automatically which we'll show in the demo there are many more use cases for this spoke including change compliance resilience testing and fix validation to learn more you can follow the link at the bottom or just go to docs.servicenow.com and search for gremlin for this conversation we're going to focus on a change automation use case which helps address some of the challenges where traditional itsm processes can slow you down because all apps on the now platform share a common data model we can easily connect dev and ops teams to give everyone clear visibility of what's happening dev teams can plan and track their work in our agile dev product or use third party dev tools and deploy changes quickly while staying compliant when something breaks responders can quickly see what changed to help identify a potential root cause and restore normal service having all of this activity in one system gives you real-time access to key metrics so you can understand how teams and services are performing to quickly adapt and continually improve with our devops product we decided to build connections to key tools you already use including planning and pipeline tools and code repositories we use information from the tool chain to automate the creation of change requests in servicenow which initiates the assurance path without having to swivel chair and manually create a request we can also use change management policies to automate the change approval process using risk and fact-based assessments the data gathered by the product can also deliver new insights across multiple teams and tool chains and auditing can become a one-button action to link all the data from ideation to production saving multiple weeks of manual effort the benefit of using devops with our change automation and itsm is that you can work as quickly as you want from wherever you want while staying safe and compliant next colin is going to show you how this works in our product and incorporate gremlin into a flow to ensure a service is resilient before deployment thanks brian now i'm going to go over a demonstration of how servicenow and gremlin can work together to help automate your change process now in this example i have two different pipelines a ci pipeline and a release pipeline a cd pipeline now these can be the same if you're doing continuous uh deployments but for this example i just have them broken out separately so for this we're actually going to start in an environment that as someone on the development team would be more familiar with which i'm going to be inside of azure devops now for this i'm going to choose my my release pipeline and from within this release pipeline i'm just going to trigger a run manually so if this gets kicked off some other way that's perfectly fine but i'm just going to go ahead and click the run pipeline now in the interest of time i'm actually going to go back out to a pipeline that's been run in the past to kind of show you what happens and how servicenow interacts with azure so i have a really simple two stage i'm packaging up my artifacts and i'm deploying them into production now as a part of the deploy stage there's a step that's been introduced that says basically talk to servicenow create a change for me instead of me having to go in and create the change manually and then if everything looks good which in this case it was then we get a result back that says yes this particular step did need a change request and that change request was successful because the goal is to actually automate both the creation and approval of the change request now in order to automate it some things are going on in service now in the background and these things are something that people on the team really shouldn't need to worry about so i've come into service now and i have a change automation flow this just will be a workflow that kicks off uh whenever a devops change is raised and it has lots of steps that we don't really need to get into um but down here i have this uh this we call it a sub flow think of it as like a function call that says we want to gather all of the the data that the change team needs in order to decide whether or not this change can be automatically approved and right now all i really have are i'm running general tests but we have an example of working with gremlin where we can as a part of the change flow create a couple of attacks that are going to be run we can schedule it to run during a blackout period and then we'll check to see whether or not it was successful if all of our attacks uh uh were properly uh defended against and if we don't you know we can send an email we can send a post a message to slack just letting the team know that in fact we we didn't have uh successful attacks that were run um but for this case you know we know that these are good and i'm going to drop this in to a currently existing change flow so this is something that your servicenow team would set up one time to just have as a part of the change so we're just going to add a new step i'm going to add a flow and i have a gremlin attack validation that we're just going to drop in now that this attack has been dropped in we're going to wire up one thing which is the configuration item that we're going to interact with so we need to know in order to keep this in order to keep this from being something that only works for one team we need to basically look it up by reference so that's been set up that's all that's needed the subflow does the rest and in the change policy now we're going to come in and we have a lot of policies that have already been set up looking at incidents and test cases things like that but now i also want to take the results of the gremlin attack validation and i'm going to drag in the success percentage drop it into the nice little area that's awaiting it for the percentage of gremlin attack success and that's now wired up for the devops uh change policy and now once this policy is evaluated for any change that we run it'll either choose to auto approve it or in this case i have it sending to a group if it was not auto approved you can also have it auto reject or send to a person that's really up to what your process looks like before the rest of the change flow runs and what that really gives you is that from the servicenow perspective we stay out of the way of the teams that are working and whatever tool you're used to but still giving the uh the people on the servicenow team the the service team the change team the ability to see exactly what happened for this particular run we can see what artifacts were deployed we can see the pipeline we see that a change was raised and was approved and also everything that happened whether it was gremlin attacks or whether it was load tests or unit tests or some other type of functional test so with that we really again allow your teams to leverage all the testing tools including gremlin to automate your deployment process while still getting all the things that the service team needs to understand for making sure that we're adhering to our governance uh and compliance policies and with that thank you for watching how servicenow and gremlin can work together to help automate that change process thanks for that great demo collin we'd like to thank everyone again for spending some time with us please visit our website to learn more and contact your account team for a deeper dive take care everyone and be safe