Go to the U of M home page
Showing posts with label applications. Show all posts
Showing posts with label applications. Show all posts

Wednesday, October 30, 2024

Tony's Tech Terms: Splunk

Splunk is an OIT-supported tool that helps us keep an eye on our applications by collecting and organizing the detailed "logs" our apps generate. When our applications run, they create a record of their activities, known as a log entry, which captures everything from normal operations to errors. 

Splunk gathers all these entries into one place, making it easier to track application performance and troubleshoot issues. By using Splunk, we don’t have to sift through logs manually to find problems—we can instead set up automated alerts that notify us whenever something unexpected happens.


With these alerts, we can quickly respond to issues. For example, if an application keeps erroring under certain conditions, Splunk can detect this recurring error and immediately alert us. This real-time notification system helps ensure that problems are identified and addressed right away, reducing downtime and keeping applications running smoothly.


Wednesday, June 26, 2024

Tony's Tech Terms

Are you curious about what happens in one of our applications when you access it via a web browser?
  1. Accessing the Website: When you click a link or type a web address, your web browser sends a request to our server.
  2. Server Reception: Our server receives your request.
  3. Routing the Request: The server has a system (called a router) that figures out what to do with your request.
  4. Processing the Request: The router directs your request to a part of the application (called a controller) that knows how to handle it.
  5. Fetching Data: The controller uses a set of rules (called a model) to interact with our database and get the information you need.
  6. Sending Back the Data: The information is sent back through the controller which then sends a response to your web browser.
  7. Displaying the Web Page: Finally, your web browser receives the response and displays the web page for you.

Thursday, June 29, 2023

Requesting TCards reminder

Please do not submit TCard applications directly to the Controller’s Office because additional local approvals are required to complete the application. All applications for new credit cards should be sent to ASRCentral@umn.edu following director approval, so the remaining required approvals can be completed. Incomplete applications sent to the Controller’s Office will not be processed, which can add significant delays to your card’s arrival (regularly 6-8 weeks).