It's time to talk about
"Troubleshooting a Failed Pipeline Run".
In this lesson, we are going to take a look
at how we troubleshoot a failed pipeline run.
We're going to start by looking at some troubleshooting
steps, and then some just general things to remember.
All right, with that, let's jump in.
So, let's talk about debugging and basic monitoring.
First question: was the pipeline able to debug correctly?
You want to hop in and take a look at that,
and if it wasn't able to run correctly, what was shown?
We also want to take a look at dashboard runs
with details of the latest fail, and we want to understand
were the multiple successes before you had the failure?
So let's jump into the portal real quick
and take a look at these concepts.
So here we find ourselves in our Data Factory studio.
And so I've opened up my Data Factory studio,
and I went under the Monitor tab here,
and then I clicked on Pipeline Runs.
So you can see here, we have Triggered and Debug.
If we have Triggered selected,
that's obviously going to show us
any runs that were triggered.
And then this is our first Debug run,
so we can kind of see what's happening there as well.
So I have given you a Succeeded and a Failed pipeline.
So we can take a look both and see what's happening.
First thing to look at is, with the failed run,
I can come over here and click on my error,
and it will tell me exactly why it failed.
So this is your very first clue,
and 99% of the time, should fix what's wrong.
You'll be able to go in here, take a look.
And so you can see here that our activity timed out
in my Copy Data activity.
Well, let's see why that happened.
So if I go to my pipeline, this is pipeline1.
Here's my Copy Data activity.
If I click on it and I look at my timeout,
woah, it was set for 1 second.
Pretty unlikely that it's going to succeed
with a really short timeline like that.
So that's just a simple look
at how we can fix our pipeline runs.
So make sure that you start there by looking at that.
And the same thing's true with Triggered.
You'll be able to see all the statuses,
go in and see exactly why it failed.
So make sure that you look at that, look at your Debug,
look at your Triggered,
and see if you can understand, from the error,
what exactly is going on.
Now, as you get a little bit more advanced,
you can come under Notifications
and set yourself up some alerts, which I highly recommend.
All right.
With that, let's talk about a few things to remember.
So if you have reached the
integration runtime capacity limit,
you're going to get some errors.
How do we fix that?
Well, we vary our trigger runtimes
so that not everything is running at the exact same time.
And we might look at splitting our pipelines
across multiple different integration runtimes.
Another common error is long queues.
If you're getting long queues,
you want to look at your concurrency limits,
and you want to take a look at general Azure issues,
i.e., is there a service outage for Azure,
or is there something wrong with your subscription?
So, those are 2 of the most common errors.
There's a lot more, and I actually want to show you
a document that Microsoft has, and it is right here.
So this is our,
-: -and I'll put this link
in the description of the video--
but this is a, "Troubleshoot Pipeline
"Orchestration and Triggers".
So this just gives you a list
of all kinds of things that can go wrong
with your pipelines.
My suggestion to you, as we finish this video,
is jump in and skim through this.
No, you do not need to memorize this for the DP-203,
but it wouldn't hurt you to be familiar
with just a quick run-through of
the kinds of things that can go wrong in a pipeline.
So with that, let's go ahead
and wrap up with a few key points.
One, the starting point should always be your dashboard.
Make sure that you hop in and you take a look
to see if there's any errors
and see if you can troubleshoot what's going wrong there.
Next, read through that doc.
That's your homework after this lesson.
Make sure that you don't spend a ton of time
memorizing those concepts.
Skimming through it 1 time should be just fine,
but make sure that you've done that.
And when that's done, I'll see you in the next lesson.