Frontier adds West Coast airport, fills 2 former Spirit routes


Frontier Airlines is making its latest push to fill the void left by Spirit Airlines.

The Denver-based budget airline on Tuesday revealed it’s adding two western U.S. routes formerly served by its defunct low-cost competitor. That includes making its return to one Bay Area airport for the first time in three years.

Later this summer, Frontier will re-launch service from Oakland San Francisco Bay Airport (OAK), where it last flew in 2023.

The carrier will make its return east of the bay with nonstop flights to one of the most tried-and-true markets of low-cost flying: Las Vegas.

It’s a route Spirit flew in the months prior to its collapse on May 1.

LUKE SHARRETT/BLOOMBERG/GETTY IMAGES

Frontier is also adding new Sin City service from Boise, Idaho — another route Spirit used to fly.

The move comes as the airline looks to win over customers hoping to fly on a budget in the wake of Spirit’s collapse.

“We are laser-focused on redefining what consumers can expect from low-fare travel,” Frontier vice president of network and operations design Josh Flyr said in a statement announcing the news.

Read more: Spirit is gone. Can the other budget airlines survive?

Reward your inbox with the TPG Daily newsletter

Join over 700,000 readers for breaking news, in-depth guides and exclusive deals from TPG’s experts

Details: Frontier’s new routes

Here’s a quick rundown of the two new (well, returning) routes Frontier will launch later this year:

Route Launch date Details
OAK to Las Vegas’ Harry Reid International Airport (LAS)

Aug. 20

11 times weekly

Boise Airport (BOI) to LAS

Sept. 10

Four times weekly

A much-needed boost for Oakland

Frontier is leaning heavily into its returning Oakland-Las Vegas route, which it’ll fly 11 times each week. I’d expect to see the most frequencies on high-demand leisure travel days like Fridays and Sundays.

Frontier operated Las Vegas service during its previous stint at OAK.

Oakland San Francisco Bay Airport (OAK). SCOTT STRAZZANTE/GETTY IMAGES

I’ll be curious to see if the carrier adds additional service from the airport. This time two years ago, Spirit had a decent-sized presence east of the bay, flying from Oakland to Las Vegas, San Diego, Burbank and Orange County, California; it also operated transcontinental service to Newark Liberty International Airport (EWR).

Frontier’s return to Oakland is good news for the airport, too, which has seen both Spirit’s folding and a notable pullback by Southwest Airlines, which has deprioritized OAK in recent years.

This year, Southwest’s total departures from the airport were set to be down over 20% versus two years ago, according to data from aviation analytics firm Cirium.

Replacing Spirit in Boise

Oakland isn’t the only place Frontier is filling Spirit’s void.

Spirit also served Boise-Las Vegas service prior to its shutdown.

Frontier already overlapped with its former top rival on more than 100 routes, executives said last month — “uniquely positioning us to recapture the demand they left behind,” CEO James Dempsey said.

Dempsey in May said the carrier would be “disciplined” in taking over routes (or assets) left behind by Spirit as the airline liquidates.

Bottom line

While it’s been a few years since Frontier has flown from Oakland, the carrier hasn’t been a stranger to the Bay Area as a whole.

The airline currently operates service from both San Francisco International Airport (SFO) and San Jose Mineta International Airport (SJC).

Related reading:



Source link

Leave a Reply

Subscribe to Our Newsletter

Get our latest articles delivered straight to your inbox. No spam, we promise.

Recent Reviews


What is Azure Application Insights?

Application Insights is an Application Performance Management (APM) service for developers to monitor live applications. The anomalies in performance are automatically detected. It also includes powerful analytics tools that help in diagnosing issues. The insights help to understand how users are interacting with the application. With the Application Insights, developers can continuously improve performance and usability.

Application Insights works on applications built with various languages like .NET, Node.js, Java, and Python. The applications can be hosted on-premise or on the cloud, or hybrid. It can integrate with DevOps processes. It also integrates with Visual Studio App Center and can monitor telemetry from mobile apps.

All the data in the Application insights service can be exported to a database or any external tools. Application Insights SDKs are available for web services hosted in ASP.NET servers, Java EE, Azure. They are also available for web clients, desktop apps, mobile devices like Windows Phone, iOS, and Android.

How does it Work?

To monitor your application, all you have to do is enable the Application Insights from the Azure portal or install a small instrumentation package (SDK) in your application. The application will be monitored by this instrumentation package. It will use a unique GUID, which is also known as an Instrumentation Key, to direct the telemetry data to an Application Insights resource. 

IMAGE

Since we install the instrumentation package in the application, it doesn’t have to be hosted on Azure. The application can run anywhere. We can instrument any background components of an application and the JavaScript in the web pages too. Application Insights can also collect telemetry data from Azure diagnostics, Docker logs, or performance counters when they are integrated into Azure Monitor. 

Interested in learning Azure Course ? Enroll in our Microsoft Azure Certification Training program now!

What does the Application Insights Monitor?

Application Insights focuses on the performance of an application to ease the work of the development team. It monitors the following constraints,

  • Request rates, response times, and failure rates – It tells us which pages are being visited the most and at what times of the day.
  • Dependency rates, response times, and failure rates – It shows any external sources that might slow the application down.
  • Exceptions – It reports both server and browser exceptions. It gives an aggregate statistics of all the instances. We can further drill down to get statistics of individual instances.
  • It will also monitor the page views and load performance collected from the user’s browser.
  • It monitors AJAX calls from web pages, users, and session counts.
  • It will show the performance of memory, CPU, and network usage.
  • We can get host diagnostics from Docker or Azure.
  • We can correlate events with requests using the diagnostic trace logs of the application.
  • It also shows the custom events or metrics that the developer includes in the code.

Uses of Application Insights

Once we install Application Insights for an application, we can get the following benefits.

  • The load, responsiveness, and the performance of page loads, dependencies, AJAX calls can be known through an intuitive application dashboard.
  • We can identify the slowest requests and determine the requests that are failing often.
  • When a new release of an application is deployed, the statistics of it can be seen through a live stream.
  • If users are affected, we can get an alert so we can check how many users are being affected.
  • If there are any request failures, we can correlate them with the exceptions, dependency calls, and traces.
  • When a new feature of the app has to be deployed, we can measure the effectiveness of it.

Microsoft Azure Certification Training

  • Master Your Craft
  • Lifetime LMS & Faculty Access
  • 24/7 online expert support
  • Real-world & Project Based Learning

Limitations of Azure Application Insights

Like any other solution, Application Insights has some limitations.

  • If your code uses dynamic SQL, the Application Insights collects the full query into Azure, which might result in uploading sensitive data contained in the query.
  • The reports show up to the server and database level. But it cannot monitor individual SQL queries on how long they are being executed.
  • When you add Application Insights and deploy the application to Azure, it won’t collect the SQL queries unless a site extension is installed for it.
  • It cannot collect first chance exceptions.
  • It cannot show common exceptions across all applications.
  • If you are using ASP.NET for your application, Application Insights does not support asynchronous HttpClient calls.
  • There is no alert severity specified.
  • We cannot configure alerts to go to specific distribution lists based on severity.

Data collection, retention, and storage of Application Insights

When Azure Application Insights SDK is installed in your application, it starts sending telemetry data from your app to the cloud. Each SDK uses different techniques to collect telemetry data from different kinds of applications. You can also include custom telemetry to send your data. Azure runs some processes called availability tests to web applications regularly. The results from the test will be sent back to the Application Insights service.

You can test which data is being sent by the SDK. You can view the data in the output windows of the IDE and browser while testing the application. The data in the Application Insights service can retain up to 730 days. Users can set up a retention duration. The debug snapshots are stored for 15 days in the Application Insights service.

If the SDK is not able to reach the endpoint, the telemetry channels store the data in local storage temporarily by creating temp files. Once the issue is resolved, the new data, along with the persisted data, will be sent to Azure by the telemetry channel.

Do you want to collaborate in the Application Packaging and Virtualization world? Begin by learning Application Packaging and Virtualization Training!

HKR Trainings Logo

Subscribe to our YouTube channel to get new updates..!

Enable Application Insights for your Application

Create Application Insights Service

Navigate to the Azure portal at https://portal.azure.com/ and login to your account. Click on ‘+ New’ from the left side menu. Search for ‘Application Insights’ in the search bar. You can see the service in the search results. Click on it to open the service and click on ‘Create’. Give a name for your service, select your application type from the drop-down menu, and select your subscription. Choose ‘Create new’ for the ‘Resource Group’ field and give the same name that you gave for the service. Select a location and click on ‘Create’.

                                         Learn new & advanced  Architect solutions in hkr’s  Azure Architect solutions course

Go to the newly created resource group and click on ‘app insights resource’. You will get the details of the resource. Copy the ‘Instrumentation Key’ from the page.

Add the Instrumentation key to the Application

Open Visual Studio and navigate to the appsettings.json file of your application. Add the below code in the file.

"Application Insights": {
"InstrumentationKey": "Your_instrumentation_key"
}

Replace the ‘Your_instrumentation_key’ with the one you copied before. It appears as a NuGet package. Go to the package.json file in your application, and you can see the Application Insights package added. You have successfully configured Application Insights to your application.

View the telemetry data

Launch the application from Visual Studio and play around with it. Stop the application. Right-click on the application, select ‘Application Insights’, and select the ‘Search Debug Session Telemetry’ option. You can see the telemetry data captured by your application. You can also see the details in Application Insights. Right-click on the application, select ‘Application Insights’, and select the ‘Open Application Insights Portal’ option.

The Application Insights portal opens up, and you can see the telemetry data collected from your application. You can drill down to see the page load metrics and more.

Microsoft Azure Certification Training

Weekday / Weekend Batches

Conclusion

Application Insights is a simple way for developers to detect and diagnose application performance issues of live applications. The SDKs vary for different applications and different platforms. Each SDK component sends different data. So choose one that is suitable for your application and install it. You can also include code in your application to send unhandled exceptions. The Azure Application Insights has a built-in map feature that can be used to identify the performance of dependencies.



Source link