First Timothy, what we're going to be looking at is we're going to be looking at a letter that was written to a pastor and instructions that he's receiving from the Apostle Paul. And so I'll begin reading to you in First Timothy chapter one at verse one. I'll read to verse four. I'm going to give to you an introduction that's going to take some time to lay the foundation for you so that you'll understand the purpose of the book and all of that. And then we're going to move into practical application of some of the things that we'll be reading here in First Timothy. So let's begin reading in First Timothy chapter one at verse one. I'll read to verse four and we're only going to cover four verses today. And so we'll begin here by looking at First Timothy chapter one beginning at verse one reading to verse four, Paul and Apostle of Jesus Christ by the commandment of God our Savior and the Lord Jesus Christ our hope to Timothy, a true Son in the faith, grace, mercy and peace from God our Father and Jesus Christ our Lord. As I urged you when I went into Macedonia, remain in Ephesus that you may charge some that they teach no other doctrine, nor give heed to fables and endless genealogies which cause disputes rather than godly edification which is in faith. For those of you who are visiting here, perhaps this is your first time attending. Let me share a couple of things as I lay a foundation and then I'll explain how we do things in terms of the way I teach and all so that you'll be prepared for the study as we give it today. What we do normally is we lay a foundation.   And so here what we have is an introduction to a book that is called the First Epistle of Paul to a young pastor by the name of Timothy. And what I want to do is I want to highlight certain things once again as introductory comments. I'll give you some things concerning the purpose of the book, the time of its writing and all. But I'm doing that and giving this explanation because I'm aware of the conditions culturally that the church today is living in. And that's one of the reasons why I think Timothy is such an important book for us to look at together. You see today we live in an age when the message of the gospel or Bible teaching per se is regarded by many as simply being irrelevant, that it's not something that really applies to me today. How do you take some ancient words and how do you practically apply those things? And so for many people the gospel is irrelevant to real life. When you speak to them concerning the message of the gospel and all they'll say to you that it's a message, that's true, but it's one message among many similar messages. So that means in essence that they don't consider it to be interesting, they don't consider the message of the gospel exciting, it most certainly isn't important. And pastors are aware of this. Passers are very aware of the way people think today. And as a matter of fact many of the pastors have adjusted their entire style of ministry to accommodate the age that they're attempting to reach. And so what has happened is they have developed different teaching styles that basically are attempts to communicate to people and to relate to people so that the people will actually come back the next week because there are many people who don't listen more than five or ten minutes at a time and if they don't like what they're hearing within the first ten minutes they get up and they walk out. And we pastors know that I've been ministering for a long time. I taught my very first Bible study, first formal Bible study in September of 1973. I have been teaching this month forty-four years. So I have some experience in what I'm saying. And there was a time when people would actually come and listen to an entire Bible study. If they didn't agree they didn't come back. But that time is far gone. That doesn't happen anymore. Within the first five to ten minutes if somebody does not relate, does not connect they find it easy to get up and walk out, which is really unheard of when I first got saved. When I first got saved I went to a place called Calvary Chapel, Costa Mesa. And Pastor Chuck Smith was the pastor of that church at that time and one of my cousins, his name was Ray, needed the Lord. So I invited him to come to church and so Ray, my sister Madeleine and I went to Calvary and we went early because you had to be early to get a seat. Because if you came late you'd be sitting in the aisle. You'd actually be sitting around the base of the platform. Some were even sitting on the platform. It was that crowded. It was a small church. It only sat about 300 people in it. But there were hundreds of kids. You'd have 500 kids coming to a church building that sat 300. So he went early and so I took my cousin Ray early and we got a seat there and as we were seated the worship happened and then Chuck, my pastor comes out to speak and as I'm seated there my cousin Ray whispers to me, I've got to go. I said, you don't know, no, no. We don't know. We're in the Bible study, Ray. He says, Dave, I have an appointment. I have to go. I said, Ray, no, we can't get up and I was three or four rows away from Pastor Chuck. Chuck goes right here. There I am and I'm talking like this and I said, no. He says, I've got to go. So I stand up and Ray stands up and my sister stands up and we have to thread our way between all these people who were seated on the aisles. Pastor Chuck looks at me, my first conversation with Chuck Smith. Young man, that's how Chuck would speak to you.  He says it to me, my first conversation. I got my crazy cousin with me. It was his fault. You know what my cousin does? He puts the one way and let's just take you home, put you back in the institution. That was my first conversation. I spoke to Pastor Chuck years, years later. I said, Chuck, I remember you saying this is the first time you spoke to me and you asked me why I took the seat of somebody. And I said, and you just let me know in front of everybody. And he says, and you deserved it. I said, that's true. That's true. See, there was a time when you actually respected what was being said, even if you disagreed. That day is long gone.  They don't care it's God's people. They don't care. They just get up and go. We understand that. Pastors understand that has happened so many times. It happens all the time. It's happened so many times you have to preach around that because that's the way the world is. I understand that. But pastors today are adjusting to the way people respond. And so they're changing their style of communication. And what has happened is some have become entertainers. And so what they do is they polish their presentation and they emphasize personality. And they're very careful to entertain those goats. They want the goats to remain. They're not feeding sheep. They're entertaining goats. And what they're trying to do is they're trying to keep them there so they can finish their sentence before the person gets up rudely and walks out. And what happens is they change their whole style of teaching so that they don't say things that discourage or offend. And I've said this many times. It's like this old song I heard when I was a kid, Home on the Range. And the church becomes like Home on the Range where never is heard a discouraging word. So they won't say anything to cause somebody to actually examine their own hearts to see whether or not they're right with God. So they have a group of people who show up because they want them there. But they're not being fed because they've changed the style of teaching to the degree that it becomes something that's more entertainment. Others have become great storytellers. They'll begin their message with a story and they have story after story after story. And the people come for the stories because it's exciting. Oh, you had this great adventure. And you did this and you learned that and you did. And oh, wow. And they like the stories. One story after another, after another, after another. But what that does is it produces a dull minded sheep who just wants to hear stories and not the word of God. Some have become like magicians.  They'd do that to the Bible. They'll stick their hand in the Bible and pull something out. It's not even there. It's an illusion. But people think it's great. I remember somebody saying to me, oh, I was listening to so and so and he was saying this and that. And I didn't even know that it was in the Bible. And I said, that's because it's not. That's because it's not. That's because they gave you some kind of illusion to make you think that it is, but it's not at all. They're a magician. And then you have others who like to ride their hobby horse. It doesn't matter what that passage says. They're going to get back to what is the thing that intrigues them the most or causes them to think about it the most. It happens all the time. And people like the hobby horse. So you have entertainers. You have storytellers. You have magicians. The hobby horse rider and passers are aware of that. Passers are aware of that. Nobody, nobody starts a Bible study with the hope that people just get up and walk out. Nobody plants a church where they want people to not come back. And so what we do is we adjust and that's what has taken place in these days. But the bottom line is, is we know that the Bible is the word of God. And it's by his word that we want to live. And that's why we teach through books of the Bible. And that's what we're going to do today. We're going to begin a series in 1 Timothy. And I want you to know what the book is. And that means I give to you introductions. That means that give to you foundations. That gives to you information so that as you're going through Timothy and reading it on your own, you can say, oh, that's why this was written. No, I can see that. And that's where this introduction is actually leading. As you look at 1 Timothy, I'll give you a few things. A few facts about it. This book was written around the year 63 A.D. It was written from a place called Macedonia. You see that in verse three where Paul says, I urged you when I went into Macedonia. The letter was written from Macedonia. When you're looking at a map, you've got Greece. You have Northern Greece and it's connected to Southern Greece, the little isthmus that connects you to Southern Greece. Macedonia would be the Northern portion by what is called, was Yugoslavia. So that's the Northern region of Greece. It was written as a letter of encouragement and instruction to a young man by the name of Timothy who was the pastor of the church there in the city of Ephesus. When you look at Timothy, Timothy was a young man who had been wanted Jesus Christ through the ministry of the apostle Paul. As we've been going through the book of Acts, some of you have journeyed with me through Acts and when we got to chapter 16, we were introduced to this man, Timothy, and we saw how he was converted under Paul's ministry in the city of Lystra.  And yet Paul had brought him to faith in Christ and that's why he would say in verse two that Timothy is what he called a true son in the faith. This man had been converted to faith in Christ through his ministry. As we read our Bible, we discovered that his grandmother's name was Lois, that his mother's name was Eunice. And according to 2 Timothy, chapter one, verse five, they had become believers in Christ. And it was Lois and Eunice that prepared Timothy to become a man of faith. Paul speaks about that in 2 Timothy 3, verse 15, when he says to Timothy, from childhood, you have known the holy scriptures which are able to make you wise for salvation through faith which is in Christ Jesus. And so, one application we get right from the beginning is this. What had happened is grandmother and mother, Jewish's who had a love for the Old Testament had raised this young man who was a mix of Jewish and Gentile and brought him up in the faith of Israel and thus they gave to him the Old Testament and prepared his heart. And that's what Paul is referring to in 2 Timothy 3, 15, when he says the holy scriptures are able to make you wise, wise for salvation. In other words, the seed had been planted, the word of God had been planted in young Timothy's life and thus when he heard the gospel it connected, God used that, his faith was placed in Christ and he became a safe man and that's why Paul can call him my genuine son in the faith. Here's something for us as parents.  One of the things that I would encourage you to is pour into your children the word of God. Have times in God's word. When my children were small from the time, they were very small from the first, all through all four of them. Marie and I would pray with them, we would pray before meals, even when they were so small they didn't realize that we were praying. We'd have them in their little high chair there. I would take them by the wrist, I'd just hold them lightly on the wrist because they want to eat and I would say in a minute we're going to pray first to Jesus and we would pray and I'd say Jesus thank you for this food and I taught them to pray and to thank God for their meals from the time they were infants. As I got older, we would have home devotions. We had devotions with my kids five out of seven days out of the week, five out of seven nights. The only two nights they didn't have a devotion as they were growing up was Wednesday and Sunday night because I taught Wednesday and I taught Sunday. They would come to the Bible studies, all the Bible studies from the time they were small because I knew that the enemy was going to go after my children. I knew that he was going to destroy them. I knew that he was going to go after their life. I knew that. I knew that it's a war for children.   I know they're going to go to a school that is not going to teach them what we're training them up in. I know that. And how are they going to be equipped to fight if I don't equip them? I didn't expect others to do that. I did it myself. And yes, when they got older they gave us a run for the money. I have to tell you. They were not saints. Some of you know my kids. You can say amen, I don't mind. They weren't saints. But you know what? They were secured through prayer. And I said, God, your word says, train up a child when he is young and when he is old he will not depart from it. In Jesus' name I'm going to keep pouring into my kids and pouring into my kids and pouring into my kids because one day it's going to come home. One day the word will find root in them and produce fruit. I trust you for this. And that's what we did. Listen, parent, teach your children. Don't expect the church to do that. Pour the word of God into them. Pray for them. And train them up in the ways of the Lord. The world will not do that.  And that's what happened with Timothy. That's how it worked with Timothy. From an early age, from infancy you knew the holy scriptures which are able to make you wise into salvation. That's how it works. That's how it works. And so that's what Paul is speaking about right now. You see, after he had gotten saved he became a traveling companion for the apostle Paul. Paul went on several missionary journeys. There are three recorded in the book of Acts and on Paul's second missionary journey he planted a church. He planted a church in Ephesus. You see that in Acts chapter 18. Now when you look at Ephesus in history, Ephesus was a huge city according to ancient standards and it was breathtaking. In its beauty, I've been to Ephesus on more than one occasion. And the ruins, just the ruins you can tell this was an amazing city. It was huge by ancient standards. It's located on the southwest coast of Turkey. It was a commercial center of what is called Asia Minor. During the Roman occupation of Ephesus the city swelled to over 250 up to 300,000 people. It was the second largest city in the Roman Empire as well as the world. It was known for its harbor, but it was also known for magic as well as the temple of Diana. And the temple of Diana when you look in ancient history was one of the seven wonders of the ancient world. One source said it is estimated that the temple measured between 350 and 377 feet long by 175 to 180 feet wide. To relate its size to modern perspective, the layout of the temple was longer and wider than a standard size football field. The temple of Diana also called Artemis was considered the first Greek style temple to be made completely of marble. It was built with more than 100 marble columns standing 40 feet high and the entire project took over 120 years to complete. So if you're doing an addition, don't complain. Paul planted the church in Ephesus but he eventually left it in the hands of a young man named Timothy. Now to minister in such an opulent and decadent society was incredibly intimidating. And so for this reason, Paul wrote to encourage Timothy to remain strong and faithful. There are places that are like demonic strongholds. There are places that have an openness sometimes to the gospel. This area here that we're in has an openness to the gospel. It still does, thank God for it. But there are other places not that far from here that are strongholds of opposition. I ministered for a few years in Claremont and Claremont is a stronghold. It's got many, it's got higher education there. It's got a real strong anti-Christian feel to it. Some of you know what I'm talking about and it's kind of difficult to reach. But there are other places that it seems that they're just waiting. Come and tell us about the Lord we want to hear. Ephesus was a stronghold. It's like if you go into some of the parts of LA or you go to some places in San Diego or you go into San Francisco, they're strongholds.  Ephesus was a stronghold and it was intimidating. And yet Paul is telling this young pastor, stay there and do a work for the Lord in this mighty city called Ephesus. Now, as Paul is writing to this young man, he's giving him instructions. And these are the things we're gonna see as we go through 1st Timothy. He says, these are the things you're to do, Timothy, expose false teaching, develop qualified leaders, teach the word of God. He says, exercise your spiritual gift, become an example, fight the good fight of faith. He says, organize the church under qualified leaders. He also says, you're to refute error by teaching the truth, encourage godly conduct by being godly, protect the purity of the church by enacting church discipline on members who are in need of correction. These are the things you need to do, Timothy. And you'll see these things as we go through this letter to Timothy. When you're looking at it and you're studying it, there's a key word. And the key word that is used here is the word doctrine. The word doctrine literally means teaching. And Paul uses the word doctrine in this letter eight times, which tells us he's emphasizing something. So someone asked, why would doctrine be so important? Why can't we just believe what we wanna believe about God? After all, some say it's not about doctrine, it's about Jesus. But that kind of comment is actually reflective of what would be called the last days because the Bible says in the last days, people will no longer endure healthy doctrine. And so when you have people saying, well, it's not really teaching we need, we need to feel closer to God, it's just symptomatic of the fact that we're living in the days just preceding the return of Christ. Why is doctrine so important? Doctrine is important because it safeguards people. Eternal life and a lifestyle that brings glory to God rests on accurate teaching because what you believe is what you ultimately do. And what you believe and do is what makes up your influence. And when you are believing and doing things that are wrong, you influence others to wrong. So Paul is speaking to him about this because it's important. We'll see in 1st Timothy 4.16 how he says to Timothy, take heed to yourself and to the doctrine, continuing them for in doing this, you will save both yourself and those who hear you. And so this concern for safeguarding proper teaching is paramount to the apostle Paul. Again, in the book of Acts, when you get to Acts chapter 20, records Paul's last conversation that he had with the elders of the church of Ephesus. Paul knew that he would never see them again. And so in Acts 20, he's giving them final instructions. And he says in Acts 20 verses 27 through 30, and he's speaking to these elders. He says, I have not hesitated to proclaim to you the whole will, the whole counsel of God. Keep watch over yourselves and all the flock of which the Holy Spirit has made you overseers. Be shepherds of the church of God, which he bought with his own blood. I know that after I leave, savage wolves will come in among you and will not spare the flock. Even from their own number, men will arise and distort the truth in order to draw away disciples after them. They're gonna come and they're gonna invade your church is what he was telling them. They're gonna come and invade.  But not only will there be people who come in from the outside, a great danger also is those who are on the inside using their influence. And it all comes because they're drawing disciples after themselves. So doctrine is important because it has consequences for now as well as for eternity. There's your introduction. Let's get in the study. Verse one, Paul, an apostle of Jesus Christ by the commandment of God, our savior, and the Lord Jesus Christ, our hope. To Timothy, a true son in the faith, grace, mercy and peace from God, our Father and the Lord, and Jesus Christ, our Lord. The way they wrote letters in the time of Paul is outlined right in front of us. It would begin, the letter would begin with the author of the letter. So he begins by saying Paul. The second thing you would see is the recipient of the letter, which is what you see when he says to Timothy. And the third thing you would see in their letter would be a blessing, grace, mercy and peace from God, our Father. And so this is the typical way that letters were written during that time. Notice how Paul describes himself. He identifies himself as an apostle of Jesus Christ. He identifies himself like this in nine out of the 13 letters that he writes in the New Testament. He's an apostle. The word apostle literally speaks of one who's been sent out and has had designated authority. So he's speaking concerning himself as one who's been sent out by the Lord Jesus Christ with the authority of heaven. He's an apostle. But he's also an apostle by the commandment of God, meaning he didn't select himself.  God chose him. God sent him on this mission. You see, we do not need to be looking to other people to appoint us. The appointing comes from the Lord himself. In John 15, 16, it says, you haven't chosen me, but I have chosen you and ordained you that you should go and bring forth fruit and that your fruit should remain. So I am an apostle by the commandment of God. In Galatians 1, 1, Paul would say, Paul an apostle, not from men nor through man, but through Jesus Christ and God the Father who raised him from the dead. So he begins by saying my authority is through God. The commandment was from God for me to be this. But he also refers to God as our savior and Jesus as our hope. So when he says, God our savior, God our savior reflects Paul's rejection of Nero because Nero, Caesar Nero was referred to as the savior of the world. And so Paul is making it clear that Caesar's not the savior of the world, God is. In Isaiah 43, 11, it says, I even I am the Lord and beside me there is no savior. Isaiah 13, 4 says, I am the Lord, your God from the land of Egypt, you shall know no God but me for there is no savior beside me. So he's saying my commandment didn't come from Rome and Caesar is not my God. I do what God has called me to do. It's what he's saying because I received this commandment from the Lord. The world hasn't been given the responsibility of telling the church what we're to do. Our orders come from the Lord and we find those orders through God's word. Paul is making it very clear that that's how it works, that we take our orders from the Lord. You can call Caesar Nero the savior of the world if you'd like as a Roman citizen, Paul was saying, but we know the true savior and the true savior is God himself. And we follow God's directives, not yours, regardless of whether somebody thinks they can force us to do what they think is the right thing to do. We don't take our orders from the world. My friend Ron is pastor of Houston, Calvary. They were in the newspaper recently because he's become a center there for the hurricane situation and all there in the Houston area. And his church has become a center where many churches, many Calvary, especially churches have been sending teams to work and sending finances to help and all of that. And so recently there was an article written about Calvary Houston because somebody from the LGBT, quote unquote community was angry because they had come and wanted to serve with the church as the church was doing its work. And they said, I'm sorry, but this is for believers. The work that we're doing is coming out of our church and the members of our church and other Christians who were coming from around the nation. And so no, we're not gonna have LGBT serving here in the church given the impression that your believers, because in fact, your lifestyle disqualifies you from that. Now that's Bible, that's Bible. And so what do they do? They call them haters.  Why? Because no, we don't take our orders from the world. You know, listen, if you wanna go out and do a work, go do it. Listen, here we go. I shouldn't do this. I'm gonna do it. Here we go.  And you see them marching, you see them hating and apparently the hurricanes that are coming is because of Trump. I read that. One of the Hollywood elites with an intellect that's equal to a stone was saying that. And so everything bad happens is because it's Trump and therefore the hurricanes really result of some judgment that's coming because of Donald Trump, which to me is really, it's really sad. It's really a sad way to think and it's so bad. But with that said, I don't see these people who are protesting. I don't see these people who are violent. I don't see these people who are doing the things that they're doing in such an angry way. I haven't seen them on any work in any food lines. I haven't seen them taking up collections and offerings and getting teams of Antifa people to go on to actually serve and help and clean out homes that are messed up. No, why? Because they're parasites. Because they take from what good people do and they only, they call us haters when in reality they're the haters. If they're so good, I'm gonna say it this way. If they're so good, why aren't you doing something good?  Why aren't you crying with those who are losing things? Why aren't you ministering to the children? Why aren't you taking what you are as a parasite? What you are as a parasite, you know, the Boy Scouts of America years ago was being infiltrated by homosexual scout leaders and I wrote a letter and wrote it to the editor and it was printed and I said, listen, I said the homosexual community has a tendency of taking something that has a tradition of doing good for many years and then they say you are excluding us from that.  Why don't you do that? Why do you have to take something that has been so good for so many years and has done so many good things for so many kids?  Listen, we shouldn't and we cannot put up with that garbage. The bottom line is is we have truth that comes from the gospel. We live for Jesus Christ and that's what we're supposed to do. That's called Christianity. That's Christianity. See, so our commandment comes from God. It doesn't come from man. I answer to a higher authority than some disgruntled individual who decides to get up and walk out on a church service. I answer to God himself and that's what Paul is saying. And we have to understand that. If you fear anyone, Jesus said fear God. Don't fear man, fear God. And that's what we're taught to do. That's Christianity 101. People don't understand that. And so I'll get off that horse and move into another, right? Jesus is our hope. Listen, he's our hope and he speaks of him in that way. He says by commandment of God, our Savior and Jesus, the Lord Jesus Christ, our hope. Without Jesus, we have no hope. No hope for eternity. Why? Well, according to Ephesians, chapter two, verse 12, once again, Paul writing to this church that Timothy pastored. According to Ephesians two, verse 12, he said to them, at that time, you were without Christ. Being aliens from the Commonwealth of Israel, strangers from the Covenants of promise, having no hope and without God in the world, having no hope and without God. You see, when we receive Christ, we're given hope and we live in hope. And our hope is not in man and our hope does not originate in what the world offers us. Psalm 25, verse five, reads, guide me in your truth and teach me, for you are God my Savior. My hope is in you all day long. So no matter what we may be going through, we go through it because of our hope. The word hope is translated, confident expectation. It isn't used in the Bible, the way that we use it in our common parlance. When we say hope today, it's like, I hope the Dodger stopped losing. That's hope. It's confident expectation. Jesus Christ is our hope. We hope in Him. We have a confident expectation. We are saved, Paul said to the Romans. We are saved in hope. And so we have a confidence in the Lord and all. And Jesus Christ is our hope. No matter what our circumstances may be, as we go through those things, God has a way of strengthening us as we go through, and why? Because we have hope. In Romans 15, 13, it says that God of hope fill you with all joy and peace and believing that you may abound in hope through the power of the Holy Spirit. We also look forward in hope to the final results of living in hope. In Titus 2, 13, Paul said, looking for that blessed hope and the glorious appearing of the great God and Savior, Jesus Christ. In 1 John 3, 2, and 3, it says, beloved, now are we the sons of God. It does not yet appear what we shall be. But we know that when He shall appear, we shall be like Him, for we shall see Him as He is. And every man that has this hope in Him purifies himself even as He is pure. So he says in verse 2 to Timothy, my genuine son in the faith. Paul had no son of his own. But he loved and treated Timothy as if he were his own. And you gotta think for just a moment how Timothy reading this, how that would have registered with his heart. That Paul is saying, Timothy, you're my son. You're my son. I don't have any children. I didn't have any. But I have you. You're my son in the faith. Allow me to give a personal illustration of why that matters. Pastor Chuck was my pastor. Chuck Smith, pastor of Calvary Chapel Coastal Mesa was my pastor for a long time. I was at a pastor's conference on one occasion. I was seated next to him.  He gave me my father who I love with all of my heart, my physical dad. He gave me my father, but he also gave me you and you are my father and I love you like a son. I was in a pastor's conference a few years ago and just before Pastor Chuck went home to be with Jesus. As a matter of fact, I believe it was the last pastor's conference that we had with my pastor, Chuck and he was seated off to the right. He used to always be seated in the same place and it was one of the very last conferences and I was teaching at the pastor's conference. There were over 700 pastors there and as I was teaching, I was sharing about loyalty and ministry and Chuck was there and as I was teaching, I turned and I looked at him. I still remember looking at Chuck. He was only just a few feet away and I said, Chuck, I want you to know something. I want you to know that I am loyal to you. That you are my pastor and I will not bring shame to you. You are my pastor and I love you. It was a time I was teaching at a men's conference in Anaheim and we would have between seven and 10,000 men in this conference and I was teaching at this particular conference and there's a stage set up and then there's the backstage area. They had some seats lined up next to the stage and then they have other seats that are in a different area and a lot of the guys are in the different area and Pastor Chuck was seated by himself in this line of chairs, just a few steps from the stairs that would take you up to the platform and I was the next speaker and so I came and I sat next to Pastor Chuck and as I sat next to him, he was shoulder to shoulder with me and I just turned and I smiled at him and he looked at me and out of nowhere as I was seated there, Pastor Chuck leans back and puts his arm around my shoulder and then drew me to himself and just held on to me like father would hold a son and I have to tell you even to this day that makes me choke up. He was my father, my spiritual father and I loved him like a son loves a father and when Chuck told me how important I was to him I have a letter that he wrote me that I still have where he says that to me and I kept it, it's a memory. I understand what Timothy would feel when he read this letter from Pastor Paul who said my genuine son in the faith, my genuine son. That means something, it means a lot and it must have touched this young man's heart. You see, Paul loved him and spoke highly of him. When you read Philippians 2, you see in verses 19 through 22 how he said, I hope in the Lord Jesus to send Timothy to you soon that I also may be cheered when I receive news about you. I have no one else like him who takes a genuine interest in your welfare for everyone looks out for his own interest not those of Jesus Christ but you know that Timothy has proved himself because as a son with his father he has served with me in the work of the gospel and so Timothy had been converted to faith through the ministry of the apostle Paul he was a genuine believer and a son to him. Grace, mercy and peace from God our Father and Jesus Christ our Lord as I urged you when I went into Macedonia remain in Ephesus that you may charge some that they teach no other doctrine. Now Timothy apparently was reluctant to stay in the city of Ephesus so Paul exhorts him to do so and he begins to give him orders that he's to carry out as the pastor of the church. Notice the first thing he says, charge some that they teach no other doctrine. When he says no other doctrine, charge them that they teach the same do not teach different doctrine, teach proper doctrine. So charge some that they teach no other doctrine. Charge some not to teach a different thing. Charge them not to deviate from the truth. Why? Because false teachers must be stopped from spreading error immediately. The New Testament knows nothing about allowing error to go unchallenged. Anything purporting to be Christian that changes the gospel is to be dealt with and quickly. And again, that's because error is never harmless. Error is destructive. Error destroys not just individuals, but families. In Titus 111, Paul said, there are many rebellious people mere talkers and deceivers, especially those of the circumcision group. They must be silenced because they are ruining whole households by teaching things they ought not to teach and that for the sake of dishonest gain. You see, the Bible makes it very clear that truth exists and that truth matters. Why, well, one, God is the originator of truth. In Psalm 31.5, you have redeemed me, oh Lord, God of truth. God is the originator of truth and second Jesus is truth incarnate. He said, I am the way the truth and the life in John 14.6. A third thing is that the truth sets us free from Satan and bondage because he who sins is a slave to sin, Jesus said in John 8.32.  An interesting thing about all of that, a fifth thing is believers are those who have a love of the truth. Now, this is one of the ways for you as a believer to measure your maturity. And this helps you as an individual to know whether you're even saved. Do you have a love for the truth? Not an admiration of it, not a philosophic interest in it. Do you have a love for it? You see, in 1 Thessalonians 2 verse 9 and 10, Paul said, the coming of the lawless one is according to the working of Satan with all power, signs and lying wonders and with all unrighteous deception among those who perish because they did not receive the love of the truth that they might be saved. It's an indicator that you're even saved if you love the truth. And this word of truth was given one time for all time. There is no need for future revelation. Jude verse three says it like this, beloved, although I was very eager to write to you about the salvation we share, I felt I had to write and urge you to contend for the faith that was once for all entrusted to the saints. One time for all time. There are no new revelations. So one of the pastor's duties is that of identifying those who are corrupting the gospel and preaching error. That's one of the ways that a pastor actually cares for the sheep. That's one of the ways that he demonstrates his love. He protects them. And Romans 16, 17 and 18, it says I urge you brothers, watch out for those who cause divisions and put obstacles in your way that are contrary to the teaching you've learned. Keep away from them. For such people are not serving our Lord Christ, but their own appetites. By smooth talk and flattery, they deceive the minds of naive people. And so there's a warning. Paul would do that. Paul would actually name names in 2 Timothy 2, 16 through 18. He said avoid godless chatter because those who indulge in it will become more and more ungodly. Their teaching will spread like gangrene. Among them are Hymenias and Phyletes who have wandered away from the truth. They say that the resurrection has already taken place. They destroy the faith of some. So he didn't avoid mentioning names by name. People by name. Listen, and I'll make this practical as I can today. Many Christians feel it is wrong to expose and confront error. Some feel it's un-Christian to do so because these people are doing such good things. That's because they don't believe that there is anything that is absolutely true. Somebody said it like this. It is not kindness at all, but the worst form of cruelty to suggest that what people believe doesn't really matter. It really doesn't matter much if they feel spiritual and do good. In fact, on the face of it, that claim is a blatant contradiction of the gospel message. Real righteousness simply cannot exist in isolation from belief in the truth. To make the case for any concept of practical good that subsists apart from sound doctrine, one quickly has to remove just about everything that is truly righteous from the definition of good. It doesn't take very long for that kind of thinking to undermine the foundations of Christianity itself. Listen, there are many today that are identifying themselves as Christians and they don't believe the Bible. There was a culture and media institute survey that surveyed 2,000 people and 87% said that they believe in God. 52% said they believe the Bible is God's word. Yet only 36% believed in living by the Bible and 15% said they lived by their own principles even when conflicting with God's. And 45% preferred combining God's teachings with their own beliefs. So that translates into picking and choosing passages that suit your particular belief. There was a TV preacher who was asked a question concerning Mormonism. And the question was, is Mormonism Christian? I saw this. I watched it when it took place. And when asked the question, is Mormonism Christian, this well-known TV preacher answered, it is. He said Mormons refer to Jesus as their savior and Jesus is my savior. So I would consider them to be part of the family of God. The secular interviewer corrected this well-known TV preacher. A secular interviewer corrected him. Some in this room think that Mormonism's Christian. Some of you do. Let me share with you some things. Let me be a preacher of hate for a moment, if I may. Mormonism is polytheistic. It denies original sin. It teaches that both God the Father and God the Holy Spirit have physical bodies.  Mormonism teaches that Jesus is the spirit brother of Lucifer, that Jesus was a polygamist, that Jesus traveled to the Americas during his three days in the tomb, that every Mormon male will one day become a God ruling over his own planet, accompanied by multiple wives, just as the God of this earth named Elohim was once a man has done here. That's Mormonism. That's Mormonism. And yet somebody's mad at me right now. That's Mormonism. It's error. It's error. And yet a pastor on TV, being interviewed, asked questions concerning this, doesn't know these things, and thus says, yeah, Mormons are my brother because he believes in Jesus. How would Paul respond to that? Well, in Galatians 1, 8, and 9, he said it like this, even if we or an angel from heaven preach any other gospel to you, then what we have preached to you, let him be accursed. As we have said before, so now I say again, if anyone preaches any other gospel to you, then what you have received, let him be accursed. That's how Paul would deal with it, because that's what scripture says. And so as a warning against false teachers, he says in verse four, nor give heed to fables and endless genealogies, which cause disputes rather than godly edification, which is in faith. You see, these false teachers were teaching fables and superstitious myths, if you will, Jewish genealogies that would puff up the family. But God's word produces godly edification. It builds up a genuine faith in Jesus Christ, and that's what Paul wanted them to know. And again, that's what Paul told the elders of Ephesus. In Acts 20, verse 32, he said, brother, I commend you to God, to the word of his grace, which is able to build you up and give you an inheritance among all those who are sanctified. Listen, as a pastor of this church, I want to give to you once again, a guarantee that I've given in the past that I'm remaining firm in that is this, I will teach you the truth. When you come here, you will get a Bible study. I will teach you about Jesus Christ. I will not deviate, I will not compromise. I will tell you the truth, because it is the truth that sets you free. And that's something you'll get from here. That's what I'm gonna do. That's what I'm gonna do, because I really believe in accountability. My accountability is to the Lord. Yes, I realize that things that are said sometimes, the way I say them, doesn't come off in the way that I feel them. I know that I come off abruptly. I know that I come off strongly. But you know what? One of these days, when I stand before the Lord, I want to say to him, but I told him the best that I could. I told him the truth, the best that I could. And Father, if I wasn't tender, well, I've cried many a tear over that, but I will not lie to you. I love you guys. I am a pastor of this church, and I will not give you compromise. Amen.


Okay platform is product. Thank you all for coming So this is a work-in-progress, right? We Oh, right. So first thing Pardon don't know those are verboten Thank you all for coming Would you please we're gonna do a quick fist of five?  Oh, nope my bad Sorry, the city of Boston would like me to announce that Know that the the locations of your surrounding emergency exits Find the ones nearest you please in the event of an emergency Please calmly exit to the public concourse area The emergency exit stairwells leading to the outside are located along the public concourse and Follow the directions of public safety staff. Thank you Okay, so no, I don't want to get to that yet Please raise your hand with a number of fingers one through five Indicating how well you feel you understand product management as Applied to a non-traditional product like a platform. So one through five and I'm gonna take your photo We're gonna do just a quick like what do you think? Okay? Get those hands up. Let's get keep them up Just yeah, and and totally totally Vulnerable there. Okay. All right, so I saw some I saw some pretty big numbers. That's awesome okay, so Pivotal customers have found a lot of value great success in managing their Pivotal cloud Foundry platforms as an internal product within their company And we wanted to enable the broader cloud Foundry community to be able to apply product management techniques to their own platforms So it came up with this MVP platform. Sorry. No Panel as product our value proposition is we assume that Delivering panel as product will result in better community product management understanding By measuring an increase in product management self-assessment So we've got the before and we're going to deliver a panel as product and we'll see the after But to deliver a valuable MVP we want to start by considering our problem space starting with our users So we're gonna do a very very brief personal workshop. So please raise your hand We we have some assumed personas because it would take very long to do user interviews and do a proper product workshop Personnel workshop, so we're gonna do a quick survey. Please raise your hand if you identify as product management Hey, we got a few okay great And that's distinct from project management.  We got some of those If you're an application software engineering, you make like business apps or stuff. Okay got One or so of those Raise your hand if you're an infrastructure or platform engineering Hey, all right. Yeah, I kind of identify as one of those myself Are you an IT leader raise your hand?  Okay, oh cool really, okay, that's great Raise your hand if you don't fall into one of those other personas or if you feel like an outlier. Oh Yeah, sorry Hannah Okay, great. So we've got a smattering that's terrific. We're gonna try to deliver a panel I've actually got some stack ranked questions here based on personas and such I'm gonna try to make this as valuable as possible to you so that our fist to five at the end looks a little better First panelists Would you please introduce yourselves? Oh, that's me. Yeah, we're gonna we're gonna so we're gonna run through very quickly with a Who yeah, are you where do you work? Yeah, what do you do and what does your wanted poster say? Yeah, okay My name is Kyle. I work at CSA insurance in Phoenix. We're a triple a insurance provider We're a hundred year old company. So we have lots of old products that need managing Let's see what I lead the DevOps and cloud platform teams That's where who and then the last one the wanted poster So I gave a previous talk and I described myself as a as a Frustrated optimist that I'm struggling through trying to bring all the value of this platform as a product to People who are reluctant to absorb value So if I imagine my wanted poster meaning I'm gone that will mean it would just probably just say patience ran out That's probably all I would say Thank you Kyle. Jay. I'm Jay snipe. I am a product owner at Liberty Mutual Right now I'm focused on defining products in a roadmap for our commercial insurance group Also, Liberty is a hundred year old insurance company with a lot of the same pains that Kyle has my wanted poster We'll say disruptor of status quo nice Kevin I am Kevin Mackett. I am a product manager at pivotal and my primary role is helping build teams that run pivotal cloud foundry like a product and my wanted poster I'd be wanted for Breaking processes that are there for processes sake Good afternoon. I'm Sean Cury. I am the minister of chaos at pivotal I As Kevin does I go out to the customers and I help enable people understand how cloud foundry can be run as a product My wanted poster would be wanted for brevity Hey, I'm Clayton cloud native midwife at pivotal I just as those last two gentlemen I go out to customer sites and help build a platform product teams Applying this stuff in the field. It's very exciting and my wanted poster I would say colors outside the lines So questions And I'm kind of directing this at the folks that actually run their own platforms Kyle and Jay what distinguishes your platform from a turnkey vendor product? Maybe we'll go with Jay first When we introduced pivotal cloud foundry well, we've been on cloud foundry for over six years now So for us what was really important is to look at the platform and how we delivered value as a Enterprise consumer of it rather than what value it gave to us natively So what we really started to look at is the user experience for the developer when they wanted to consume the platform So how do they build and integrate with their pipelines? How do we integrate our enterprise identity solutions into the pipeline? How do you make it easier for a developer to get a vanity URL, which is painful So really taking a look at that end-to-end experience and that value comes from what we build on top of the platform itself Yeah, I mean it's it's really easy to identify The lack of value that any turnkey supposedly turnkey solutions providing the enterprises full of them from API gateways To whatever else, you know push button deploy code things are generous I should say push button generate code deploy our nightmares so, you know the I Mean, I guess the biggest value is the cultural impact it has in an engineering team right to take ownership and of writing code shipping code monitoring applications Being closer to your customer experience and being able to be more adaptable to shifting demand So in my mind that the main Value is platform as a product is that you know the the apps value is really, you know Temporal we don't know how long it's going to be valuable that particular app And so you need platforms that are can respond to shifting demand very quickly And you can change your mind on one thing the next day and not you know It's like oh we have this three-year commitment to this bit of infrastructure that we just bought but the market went that way and your host to Use a technical term your host Okay So, how do you know you're building the right thing for the right people? And I'm gonna ask Kevin this one because I think he's got a neat technique The the most important thing is understanding who your customers are so when we are working with platform teams He's a couple different exercises one of the things I like to do is go through and build out personas We do persona workshops and just understand Exactly what kind of customers that we have sometimes we look at individual developers and kind of different types of Needs for developers. I didn't experiment my last engagement where we actually set up personas as App development teams and just understanding what kind of things are important to them What kind of technologies they may want to use and use those techniques to help inform the The roadmap and the backlog Can you give us an example of a cup persona or two? so I think one an interesting one I was showing at lunch actually was the the cloud native Mavericks, so being a group of engineers that are in a in a innovation lab that they really want to have Just enough to to get going and and not have too much of a corral We had a similar kind of persona that we wanted to differentiate Which was just cloud native not the cloud native Mavericks and those were folks that Wanted to know kind of a specific traditional way of doing things have a little bit more informed opinion and Understand what was wanted from enterprise architecture and and what had happened traditionally in the company so they wanted a little more guidance and Helped us to find things like what you know giving them an account on the platform and providing them with the CI CD framework and giving them an example spring app that was Opinionated to the specific customer so as as a starting point Awesome, so yeah, it's just a helpful exercise to keep up on the wall in the in the room that everybody's working in Hopefully all together to just remember who your customer is Just the one thing that I really like To ensure we're building the right thing is our demos Right get get your product out there show people what you're building and get them all into the room So that they can give you feedback immediately Awesome. Yeah, keep those feedback loops tight And I want to throw one more thing out just because you had mentioned MVP earlier the concept of a minimal viable product It's you build just enough to get your customer in the door So we like to come up with thin slices of functionality Get it out before we've invested a ton of time into something and get our dev teams in in the platform For whatever the the new feature or whatever it is that we're providing and really confirm our assumptions So we want to make sure that you know, we're not going off on some You know six-month project to build something and then it's not at all Well, my favorite line is that's exactly what I asked for and not at all what I need So we just need to need to get the customers in the door as quickly as possible You know, it's almost like we practiced this in order, but we totally did that's a perfect segue. Thank you, dude So Jay How do you measure that success what You know, how do you determine the success of an MVP or you know delivery? Do you how do you measure value delivered? How do you gauge sentiment? What what's what is what is? Measuring success look like for you. Sure So we really started to look at data-driven decisions and starting to measure things incrementally as we deliver different value so for us a real quick use case here as we first started looking at the user experience and really when we talk about a user from a Pass perspective, it's our developer. They are our customers. We need to make that experience good We need to keep them working on business problems and not platform and enterprise problems So when we first measured the amount of time it took for a developer to come to Liberty Get the necessary IDs and access they needed to start building and deploying on to our pass pattern It took about 22 days We started looking at how can we start to cut that time down because our ultimate goal is to be down to Deploying on to pass in a single day new developer. No identity Just all they have is really an organization that they exist in how do they start deploying? So we started with identity. We started to introduce secrets Into that same pipeline Although there are different teams supporting that they all come to the same Console to start that process. So they're not going to one request to one team and then one request to another There's a single point where they start and they really end there as well So we've measured that down and over the past year. We have gotten it down to a day for a simple use case We can deploy new user Interproduction in a day. That's amazing. That sounds like a startup Okay, so Kyle what is measuring success look like for you? Yeah, a lot of the same a Lot of the same measurements there I'd say, you know From where our engineers are coming from the the bar isn't very high. So that you know, it's It's kind of easy to beat but we want to challenge ourselves, right? So and obviously the platform unlocks a lot of that just kind of nature of the design but you know the ecosystem we've put around it is important to us So there's probably two dimensions that are most important to me the onboarding process for teams So, you know as we onboard new application teams, you know We're literally kind of you know starting a counter and seeing like how soon are they getting you know They should be in slack the right slack channels They should have the right access to you know PCF spaces and users and all that type of stuff And so you know a pipeline should exist even if it's a you know Just a templated app in in the in the build pack They're gonna use or whatever like, you know, we want that to exist out, you know in a day, right? And so we're we were we're measuring that and then as that You know pipeline expands as that team starts, you know their environments proliferating and they're getting the prod You know, we measure that time from the package build time So engineer commits code package is built to the till the time it takes to land all the way in prod. What is that? build to prod KPI for us Our most optimized pass of 38 minutes for you know from the build all the tests to run Deployed through all the different environments and into prod 38 minutes So then we baseline that for that team and and there's a little you know monitoring alerts on that if if all of a sudden It goes up to an hour, you know, people are getting slack alerts like what why did you inject friction on purpose? Is it is that we're getting value out of it or is it you know just? You know noise So yeah, those two dimensions are what we pay attention to awesome So I'm gonna I'm gonna cram this last question and was to and I'm gonna make it one If we could pass the mic back down, we'll start with Shawn this time What do you think is maybe the? No, I'm just gonna skip to that one If somebody came to you and asked hey, how do I even platform as product? What's the one thing you would tell them to start with? t-shirt T-shirt awesome, okay Kevin t-shirt brandy. Okay. Hi. I would say start with knowing who your customers are. That's Instead of building what's interesting or looks good on your resume or whatever to like Know who your customers are sweet I guess I would say from an enterprise perspective where we know who the consumers are of a product like this I would start with what are their pain points so you can start solving those for them first Um, maybe I'll I'll tackle it from another angle. I'd say investment is not is a Difficult it it's a new form of investment that enterprises aren't used to You know they well at least our enterprise is very project-based investment, right? And so you like go build this thing and but we're talking about a platform that enables to build all the things and So it's a different form of investment that it takes and it's a different makeup of people, you know to know your customers that will cause a particular type of Person to be able to do that management and it's of engineering background to be able to navigate You know the demand is it like out of left field your request from application teams? so there's a lot of unique roles and and An investment challenges with with just calling it I mean making stickers in the t-shirts Yes, but then I also need to hire people to staff that product in a way. That's probably pretty That is new for our enterprise, and I think a lot of enterprises Okay, so audience questions, please raise your hand and I'll bring you a mic Hi My question is around the minimum viable product How does one determine that and you know when we talk it when you're talking about rolling out slices of functionality? in terms of legacy Infrastructure you either had an ESP that worked or you had an ESP that didn't and there really was no layers of it same for an app server or a Database so I'm trying to wrap my head around slices of functionality And I'd like to ask whatever panelist answers to try to keep it brief So the things that we think about when defining MVPs are What's the body of work? That's the least amount that we can do that delivers some value So how do we get our app team into the platform? Even if it doesn't completely work, you know, we tend to look for folks who You know are more interested in kind of being on the bleeding edge obviously But can they like for an initial stand-up of the platform it might be? That they can push an app, but they don't have You know a lot of the services and things that they need installed, but just kind of confirm okay, we can get an app in and we also consider functionality and Trying to exercise risk as early as possible if we've got something in a project. We're looking at where like this could be a problem we want to try to Exercise and mitigate that risk as soon as possible And another concept is we like to try to have parallel work streams as well But to go to the specifics of your question It would really be that instead of doing like a full-blown High availability kind of situation where you can push to production and have everything ready to go It's doing it in like a sandbox environment or something first and we're gonna do Kind of getting just enough to be able to get someone in Exercise it may be a very specific set of use cases knowing that you know, it's not gonna do everything that's needed for the whole Enterprise it's not going to be production ready to go It's just getting them in and getting feedback from them and testing those assumptions because it might be You know something like if you're gonna implement some kind of a new mess messaging queue or something like that and you Go and build the whole thing out and say okay. We're open for business. We're in production in It's like well. Yeah, that kind of doesn't do exactly what we need or you know, it's a problem It's getting just enough in just the environments would be one of the one of the recommendations and great job That's just enough of an answer who else? Hey, so How did you guys gain these skills? Is there any? Sub community within the cloud foundry community for product product management. Yeah, I mean, I don't I don't know that There's any sub community. I'm very lucky that I work at pivotal and I have wonderful people who've been doing this at labs for a Long time teaching me how to do that. I know we have a product managers playbook I Don't know if that's public, but I will take a look and if it is I will post it up on Twitter And if anybody knows about sub communities, it would be Sean Kerry You can also John Cutler has a great product manager you could follow on Twitter And I think he has a video about Applying product management to an invisible like an internal product Who else? Yeah As you were talking you gave me an idea of another question one is in product management How do you view competition and prepare yourselves for it and the other is? We talk about failing fast. How do you prepare for backup recovery scenarios? Is it different than in the non-pass world? Cool. I didn't the first part of that question. What was the first part competition? Yeah, so Yes, it's kind of a hard question to answer because I think competition exists at an enterprise Among other projects or products. So it's a matter of making sure the right Conversations are occurring when a team is making a decision on whether or not for example, they're going to deploy to Pivotal or PC a cloud foundry or if they're going to deploy to something like docker So it's really getting the right folks in the room to have those conversations to make the right decisions For the application itself. I guess that's where I would look at competition from an enterprise perspective is Understanding, you know, or do they even just deploy on AWS for example on an EC2 instance? And then from a business continuity perspective, it really depends on how you manage and build out your platform itself From a cloud foundry perspective, you could run it across multiple regions in AWS You can run it across multiple regions in your own internal data centers and run things active active or Have a you know pilot or a warm backup to go to We do both at Liberty. I could talk a little bit about the competition factor so There is that in I encourage it like if you want if you want to deploy on something else be my guest but I make the barrier to entry for PCF very very little right and Now the barrier to entry to get to prod is much more rigor But just getting them in the platform getting deployed cloud very very little and what I've found is Combination of the of the value That they get out of the platform The business value it provides the ease of use and the enjoyment they have in the platform The demand drives itself right so we don't we don't really lose those fights You know with nobody's banging down OpenShift store because of the great developer experience, right? so Although it exists there, and it's a you know, it may be an option for some teams I just really put the power on the hands of the app teams like just try it and see see if you want to stay here All right. Thank you very much. I'm sorry dude. That's a minimum minimum viable panel right there Minimum viable panel to be an advocate for the platform So if if I could get a a last So we have a before fist of five We're gonna grab an after fist of five how well would you say you understand product management as applied to a Non-tangible product such as a platform raise your hand with a number one to five fingers product management For a non-traditional product Okay, I saw some numbers go up good deal. Okay, so I'm gonna I'm gonna I'm gonna early declare it maybe successful Thank you very much. Oh Fancy that's supposed to be a thank you hands Thank you very much to the audience for help us to helping us to deliver this 1.0 of Panel as product. Thank you distinguished panelists for contributing your knowledge about product management applied to a platform and If you would like to continue the discussion please remember that roadmaps as any good product manager knows our conversations not commitments, but We're road mapping to present 2.0 of this panel as product at spring one platform By pivotal in September in Washington, D.C. And if you were to use the discount code up on the screen here Or in the slides attached to The presentation on the website you get a discount to come to spring one. Thank you very much


Hello everyone. Thanks for joining today's session and today's session is about tips and tricks to migrate from eager to open telemetry. So first things first, how many of you are using eager already? Okay, open telemetry. Have you started using open telemetry? Nice. Okay, then I think you will understand most of the eager parts and open telemetry parts that I'll be discussing today. So the agenda for today is prerequisites first setting the ground correct first like what are the expectations from the talk and other things and why we have to migrate and we will also go through a brief architectural overview of both eager and open telemetry and we will be talking about levels of migration. And I also have a demo on how we migrate an application. And the last one is eager and open telemetry boundaries. So today everyone is a bit worried and confused that how and where do I plug eager over open telemetry. So about me, my name is Vinit Pothlopati. I'm a product manager at timescale. I work on the observability products at timescale primarily focused on prom scale and tops. I'm also a maintainer of open telemetry operator. So if you're already using an open telemetry operator would love to hear out your experience. And if you would like to check out the products that I work prom scale and tops, they are open source. So the links are shared at the bottom. It's timescale slash prom scale and timescale slash tops. Okay. So the prerequisites. So throughout the session, I'll also be using Tom as hotel. So open telemetry synonym or a short form as hotel. So the commonly used phrase. So I'll be using that more often. And the stock is focused on traces. So open telemetry is also getting into metrics logs and other things, but we will be confined and focusing on traces. The stock isn't intended to push the migration. I'm not selling anything here. I'll just share what are the ways how you can mix and match the things and what are the upsides of migrating. And let's understand the components first before we get into the talk. So we know there are multiple components involved in tracing both in eager and open telemetry. So the instrumentation layer usually has API and SDK. So in eager, we use open tracing API and the SDK is eager client libraries. And the agent and collector is all eager. So eager also has an agent and collector and it also offers some native storage options within the collector. Like Cassandra elastic search and there is a GRPC based mechanism to plug the external databases as well. And eager also has a visualization layer, which we'll be discussing later today and how it helps you to visualize the traces even if you're using open telemetry. And in open telemetry, all it has is the instrumentation layer and the collector layer. So eager is all the way from instrumentation to storage and visualization, but open telemetry is on the instrumentation and collection stage. Okay, why you have to migrate. Now we have been hearing eager and been using eager for a while and eager has served really well for most of us and people love eager and open telemetry has been announced in 2019 cubicon and so exactly it's like four years in San Diego. And since then the project has been matured and it's expanding itself into different observability signals and adding new capabilities. So let's discuss on what are those capabilities and why does migration would make sense. So the first thing is eager client libraries have been announced and off life support earlier this year and eager community and the maintainers also are supportive and advocating towards open telemetry SDK. So if you're using eager already have to move from eager client libraries to the open telemetry SDK and will be briefly talking on how to do the instrumentation layer migration. And the second one is open telemetry is a new standard as we all know for instrumentation and collection of data. So it takes some industry best practices that were part of open tracing open census and all, and it also adds new capabilities that were not existing in eager instrumentation side. So and the collection layer is really rich it gives you options to configure different sources and destinations to ship your data. And, and the last thing is open telemetry does support auto instrumentation which means you don't have to do any code changes you can just run a sidecar and it just works. So levels of migration. So there are two levels of migration one is the instrumentation layer the other one is the collector layer. Before we get into the migrations and how it's done. Let's do a quick walkthrough to the in eager and open telemetry architecture. So the first slide is the eager architecture you can see on the left side. There is an application the eager client and the eager agent so the application is instrumented using eager that's and the spans are being pushed to eager agent and from there you can see there is eager collector and the database and the UI. So this is the complete ecosystem and the components that are involved in eager architecture and the spark jobs are something very optional if you need them you can run. Coming to the open telemetry architecture so here in the open telemetry architecture we do not see the UI layer or the storage layer as I said that's all about the instrumentation and data processing pipeline which is open telemetry collector itself. So you can see here open telemetry collector being run as an agent so. So there is so much of confusion between this agent and collector so the collect the agent is something if it is ran within the host or as a sidecar to the application then we say it as an agent but it's the same collector that's being. Running and collector access a centralized processing pipeline where directly or applications can send the spans to the collector or your agents can send the data to the collector. Okay let's start with the instrumentation layer so you can see in the instrumentation layer as I said there is this API and SDK so. So to understand what are the components involved in API you can see this image it has the tracer API context API and the meter API so the meter API is for metrics. And in the SDK you can see there is this propagator span processor and aggregator so these are the functionalities that the API and SDK offer you during the instrumentation. So as I said the migration can be done in instrumentation using two ways which is open telemetry shim and complete re instrumentation so we will be doing a demo and discussing more about the re instrumentation but there are libraries already available in the internet on how to do the open telemetry migration using the shim. There is a blog post and medium which uses the Java application as a demo to migrate from open the eager client libraries to the open telemetry using the shim. So the shim is all about it consists of set of classes that implement the open tracing while still using the open telemetry constructs so with a very minimal code change like the blog post that's been. Authored by Jurassic is published in the internet so it's already available and it's just hardly takes five minutes to migrate by just swapping out the dependencies and imports and the second one is it's all it's also helps you to do to get on to the open telemetry SDK in no time you don't have to do the complete re instrumentation. So if you have less bandwidth and if you want to use some client based sampling in the open telemetry or you want to use open telemetry SDK for some reason you can definitely start with shim. And this is the blog post that's been referencing to that's been mentioned here and the complete re instrumentation so why you have to do the complete re instrumentation so the complete re instrumentation offers a hotel as a package. So you get all the capabilities right from the scratch from the code of open telemetry the semantics and in future you can also expand your open telemetry instrumentation into metrics and locks. So this is just a starting point for you if you get started with open telemetry and it's also easily integrated with auto instrumentation application so if you if you want to do an auto instrumentation for few applications. And if you have other applications if you which you need more granular details so the auto instrumentation gives more often higher level or traces and spans with manual instrumentation you help you'll have more flexibility over what you want to capture and what you want to measure. So it easily gets integrated with auto instrumentation and the normal apps. So that's demo time let's just get started. So my demo is as a clone from open tracing tutorials so there is an open tracing tutorial in in GitHub authored by Yuri to understand how the instrumentation works so I'm just taking the same application. I'll be showing you what's the eager instrumentation like and how's the open telemetry instrumentation is like and it's a very simple app so we have a greeting client and we have a formatter and a publisher. So the greeting client basically sends a request to the formatter and the formatter basically formats the string and then greeting client publishes the string to the publisher just to do an STD out. So the demo is available in this GitHub repository so I just pushed the demo to the GitHub. Okay. I hope the demo works. Okay. So let's jump into the code before we run it and see the differences. So I have the eager application here and this is the eager client go. So no this is a client application which basically sends the request to the formatter and the publisher. So here you can see it's all the normal code that's nothing fancy it's a main. Here you have the main and then the interesting part is here in the tracing you have to see the init tracer so we all know that if you want to start with the tracing there is an init function which basically gives you the tracer and then you start using the tracer referencing it across your life cycle of the code. So here we have started instrumenting and we are saying okay start start span and then finish and here we're also using the baggage as an example how you can set the baggage to do the context propagation and pulling it. So if you do not know the feature baggage so it's basically it gives you an ability to attach metadata during the context propagation without a need to change the API. So if you have to send some metadata from your application a to all the way down after four requests you can just put it in the context and it just flows through the last application that you want to send it. So without any disturbance or changing the intermediate applications to capture it and forward it forward so it just gets attached to the context. So here we are calling the format string function and it's making an HTTP call to 8081 and we are injecting few data. So some data which is context and HTTP headers and this is HTTP headers carrier here and yeah we are doing a request and yeah then we are also calling the print hello which is a publisher service here is the publisher service. So yeah and the publisher the format or service is nothing but a server just running just waiting for the request to format the string and send it out. And if you see the publisher service the publisher service is all about just take the request and do an STD out. Okay so first we will run the eager all in one which is which basically runs the eager UI eager collector and in memory storage by default. Hope the font is visible. So the eager collector is up eager all in one and now let's let's run the eager application. So now I'm first running the publisher go run publisher dot go that's up. So so I'm sending a string as a greeting called hello to a cubic on from my client to the format and then publisher. So we can see now the format is running the publisher is running and the client is here. So first let's check the eager UI. So as I just just started the collector so now you can see. Okay there are no services or no data because we haven't yet pushed the data to eager. It's just the eager UI eager query spans itself. And now I'm just doing hello cubic on and the demo just works as this is authored by Jurassic. Like this is this is not not just a view. So it's from open tracing demo. And now let's check the traces here. So the traces are here and you can see it says hello and you can see the request has went from hello world to format or to publisher. Now let's just check the open telemetry code and check how it works. So I'll be a bit quick here. Yeah. The open this is the open telemetry instrumentation. So now you can see you have used the hotel trace baggage and all the inputs here. So I'm not using anything from eager or open telemetry and it's it's the same. You just need the tracer and then you can start the context and I feel a few areas that's even simplifies for example doing the context baggage and headers. It felt easy for me at least in go. And here we are doing an HTTP request to format or and here you have publisher. So let's now run open telemetry and check the spans. Okay. The format is up. And now let's do the same from the client but that's instrumented using hotel. Okay. So I'm just doing the same now. Hello cubic on. As it's saying. Did I change anything? No. Okay. I'll just give it another 30 seconds. Let's just check. Let's just check. Did the spans come out? Yeah. The spans aren't out from open telemetry yet. Okay. I think I got it. Yep. Now it just works. It says the comma. Yep. Now you can see the greeting client. And it's just a few seconds ago. It's been it has come from the open telemetry. And here we can go to the format or service and check the tags. So now here it says go client and it's instrumented using the library open telemetry.io. So these are the spans from open telemetry instrumented using open telemetry and they're the same. So this is what I wanted to show. It's a very small demo, but it includes all context propagation using the baggage doing an any trace and all like the basic stuff that we use during the instrumentation. And yeah, that's that's the demo I had just to show how easy it is like to run and use eager alongside open telemetry instrumentation. So now the eager collector is running and the recent feature in eager has supported ingesting the OT LP traces coming from your application. So the data is coming in the OT LP format as the exporter. And now we are pushing it to the eager. And another interesting fact that I messed to explain is that okay, if you see the tracer here you can I have written a code in a way that you can. Okay, you I have written a code in this way that now you can configure the eager endpoint or open telemetry endpoint. It just uses the any tracer if you want to use eager endpoint you want to send to the eager. It's it's this in it provider for eager. If you want to use open telemetry, you can use open telemetry. It's just logic to send traces that are being instrumented using open telemetry in both eager and open telemetry formats. So if you have some limitation on the back end that you have to send traces only in the eager format, you can use something like this and it just works. Okay, and the question comes as the context propagation like now you have 10s of applications that are already instrumented using eager and you are starting a new application from scratch for the development. The always the question is do I need to start with eager or do I need to start with open telemetry. So the recommendation is you should start with open telemetry and the context propagation just works because eager support eager supports the eager B3 and W3 C context propagation and open telemetry does support all three. But if you have different applications talking to a same application in different context propagation, the open telemetry SDK also supports enabling or using multiple context at the same time. So if application is instrumented using open telemetry, it can understand it can receive the request using the context propagation eager W3 C and B3 at a time. So you don't have to just stick with only one context propagation. So it just works and there is an article in medium written on explaining the same how you can do mix and match of context propagation between the applications. Okay, the impact. So now we have seen the migration and how you can do the migration. Now what's the impact after you migrate so obviously you have an improved tracer implementation as I said the baggage and other things just work and the switch to the open telemetry SDK. While using the open open tracing is also a possibility as using the shim just makes this easy for you. And there is also an improved performance I keep reading in the read me and in other places. So the open telemetry SDKs are more performant and access to open telemetry framework plugins. So we are there is each language has its own way of integrating into the SDKs. So it has feature rich framework plugins. And now let's understand migrating and the collector layer. So as I said we have two levels of migration one is the instrumentation layer that we have seen that's the code. And now we will see the migration into open telemetry without touching the code or without disturbing your applications. The usual architecture when you're deploying eager collector and on the left on the right you can see how you can add open telemetry collector into your existing architecture so you don't have to do any open telemetry code changes. In your applications you can just use open telemetry collector because open telemetry collector can receive the data from eager and different formats. So we'll be talking about how you can configure the collectors in the upcoming slides. But this slide is all about if you have an architecture has left eager collector your applications are sending traces from eager to the collector. And it's going to the storage storage back in all you have to do is put an open telemetry collector in between the applications and eager collector. So the question now comes is why you need an open telemetry collector when you already have an eager collector. So the open telemetry collector eases the data collection pipeline. So if you have metrics traces logs all coming into from your applications you can just run open telemetry collector and it can do it can process all this you can configure the pipelines. For example you can also use span metrics processor which is which basically generates the metrics out of your spans and the processor is available in the collector. And here in the bottom I'm just putting a storage back in as prom scale. So it just works with open telemetry and eager. And let's understand the differences between the eager and open telemetry collector. So the eager collector has more flexible sampling whereas open telemetry collector has sampling processors to but the eager collector has more in terms of for example the adaptive sampling has been released in eager one to six so it's available in collector. I'm not sure it's there in the open telemetry but yeah you have wide options for you for the sampling in eager collector and in eager collector you have entry storage options where you can use Cassandra elastic search or use the GRPC based storage plugin for the back end in open telemetry collector as I said you can use receivers exporters and process which helps you to build the data pipelines coming from different sources to the different destinations. So this is the hotel collector configuration you can see on the left it has receivers exporters and services. So in receivers you basically configure what are your sources where will you receive the data from and in the exporters you will basically configure where you want to forward the data to in services you will basically map this receivers and exporters to build a pipeline. So on the right hand side you can see my open telemetry collector is receiving data from applications which are instrumented using eager and on the middle you can see the applications being instrumented using open telemetry and they also have a Prometheus receiver which can scrape the targets to get the metrics so you can just configure the receivers and it just works and even during the exporters you can parallely stream the data to your SAS back ends or in in-house storage systems anywhere so you can also duplicate the data between systems and if you want to move away from one storage engine to another there is zero lock in all you have to do is change some configuration in the open telemetry collector and it just works. So this is the anatomy of the open telemetry collector so you can see if you see the collector on the left side it's all receivers it's otlp receivers can eager receivers so if you have any legacy applications or any other applications which are sending you some data in different formats otl collectors should definitely have the receivers for them. I think there are already like 20 plus receivers in the open telemetry collector contrary we can just use them and these are the exporters and you also have processes where you can translate the data do some kind of sampling filtering and everything and the exporters basically map this data or send the data to the back ends and the impact so if you use the open telemetry collector as I said this makes the transition much easier and it's easy to start it's all about just running the open telemetry collector and it's it gives you the ability to build the pipelines on how you want to send the data and where you want to send the data and all yep and in now you have seen in the in the second migration which is okay you can add open telemetry collector and with your eager collector so now we will also see how why you have to use otl in the eager so you can receive data from multiple sources and process the data using wide data processing tools and you can also export it to the multiple back ends and it also supports metrics traces and other things so here you can see it's the same but here we are adding the open open telemetry collector just in front of eager collector so that it just works it just sends the data to the eager collector whereas in the past we have seen we are just replacing the eager collector with open telemetry collector so it just works so if you have any storage back end that's compatible with open telemetry collector you just put the exporter saying that hey I want to send the data to Cassandra or prom scale you just configure the exporter and it just sends the data here if you are using eager in memory or badger storage you can still use the eager collector but all you have to do is configure eager exporter and it forwards the data coming from your applications to open telemetry collector to the eager collector and the impact is you can get best in both the world so you can if you have any sampling mechanisms that needs to be done you can do a sampling in open telemetry collector and you can do a sampling in eager collector too but it gets complex you just need to take some conscious decisions on how you want to do but you can leverage the in memory and badger storages and eager also offers a g rpc based remote write plug-in so it just plugs into the databases that offer that integration and querying and visualizing the traces so if you move to the open telemetry collector there is no path to how you connect to your traces how you visualize the traces and where do you store the traces so the open telemetry project is all about collecting the data instrumenting the data and collecting the data whereas with eager you can use the eager ui2 to visualize the data so if you are moving from eager to open telemetry you should make sure how does your eager ui2 integrate to for querying the traces and these are the otterland eager boundaries so on the left side you can see its otter is all about the api sdk and the collector whereas eager is the query and matured native storage back ends so in future the eager will be evolving into a platform for traces whereas open telemetry will be more like instrumentation and a collection pipeline for all the observability data and in conclusion all I want to say is start with otter in some capacity it could be the instrumentation layer using the shim or it could be a complete re-instrumentation or you can just introduce the otter collector and start using the span metric processor other features from the open telemetry collector and that's all I have thank you thanks for joining my talk before I end my talk I just want to just show you the eager ui has recently launched a monitoring tab which can give you which can visualize use this red matrix coming from your spans so now you can with open telemetry collector you can use the span metric processor it generates the matrix and you can send it to a Prometheus back end and the eager ui directly queries the data from your Prometheus and visualizes this so this is not built it's all out of the box built by eager ui all you have to do is run an open telemetry collector and configure this span metric processor so it's really cool I just wanted to show it if you're using eager you can leverage this feature yep and let's get back to questions I'll be around yeah if you have questions just you can join me


Thank you. Why do you think your command was inconsistent at times tonight?  No, I was just I was just missing spot You know, I wasn't I wasn't really making good pictures like I wasn't making computer pictures It's no secret that team can hit just how tough is it to navigate yourself through that lineup I mean to be honest like I just feel like that second inning was the inning that kind of got me out of the game But besides that, I felt like I thought about pretty good I mean, I went like well 90 something pictures tonight. I think I'm pretty built up Basically, you feel good.  I went out there and give my all, you know It's the hardest thing about pitching to George Springer. He seems to be able to get the ball wherever he thought Our first in my life when he was in years. I mean tonight. He was just he was in another world tonight He was he was hitting the wall pretty good He got a couple hits kind of were kind of lucky I would say that but I mean he wouldn't want 5-4-5 That's that's pretty good Like right now people are gonna say can he handle pitching in New York that that's actually like a big narrative here What would you tell people about you know your first time in the Bronx? Were there any of those emotions played into the performance today? A lot of emotions come in Yankee Stadium, of course. I want to go out there and do my best This is not my best. I haven't been doing my best, but This is not the end, you know, I'm I'm gonna go out there and Sunday, I'm gonna take for sure. I'm gonna go out there and give a hundred percent every time I'm gonna give my all and that's what I've been trying to do right now