- Real-life stories of blameless post-mortems in action
- An understanding of why blaming members of a team for an outage or issue is counter productive
- Actionable steps to help you perform post-mortems in a blameless manner.
Puppet Camp Portland: Nagios Management With Puppet (Beginner)Puppet
This document discusses managing Nagios monitoring with Puppet. It describes key Puppet features like exported resources, Hiera, templates and Facter that help avoid monitoring gaps, keep configs consistent, and learn Puppet. It provides examples of using these features to define Nagios hosts, services and configs dynamically based on variables. While existing Nagios modules exist, the author wanted one that automatically adds/removes hosts and uses host/service groups. The full implementation combines Hiera, templates, facts and exported resources to dynamically build configs.
The Unrealized Role of Monitoring & Alerting w/ Jason HandSonatype
In today’s world, a company must be a “Learning Organization” in order to be successful and innovative. Learning from both failure and success, in order to implement small incremental improvements is critical. But until you implement and apply new information, you haven’t truly “learned” anything and you certainly haven’t improved.
According to the 2015 Monitoring Survey, most companies leverage metrics from monitoring and logging purely for performance analytics and trending. If high availability and reliability are important, they also leverage metrics to alert on fault and anomaly detection. Despite these “best practices”, the metrics are primarily only used as context to keep things “running” or return them back to “normal” if there’s a problem. Rarely is that data used as a method to identify areas of improvement once services have been restored. When an outage occurs to your system, you will absolutely repair and restore services as best you know how, but are you paying attention to the data from the recovery efforts? What were operators seeing during diagnosis and remediation? What were their actions? What was going on with everyone, including conversations? A step-by-step replay of exactly what took place during that outage.
This “old-view” perspective on the purpose of monitoring, logging, and alerting leaves the full value of metrics unrealized. It fails to address what’s important to the overall business objective and it lacks any hope of seeking out innovation or disruption of the status quo.
This talk will illustrate how to identify if your company is making the best use of metrics and ways to not only learn from failure, but to become a “Learning Company”.
Icinga Camp San Diego 2016 - Unrealized Role of MonitoringIcinga
The document discusses the unrealized role of monitoring and alerting in driving learning, innovation, and continuous improvement. It argues that underutilizing monitoring data prevents organizations from learning from their experiences with failures and successes. By continually understanding events and responses over time through monitoring, organizations can take actions that lead to resilient systems and high availability. The key is shifting focus from just maintaining systems to also improving and innovating based on lessons learned.
Failure as Success Devops Roadtrip Seattle 2016VictorOps
'Failure' as 'Success': The Mindset, Methods, and Landmines
J. Paul Reed
Release Engineering Approaches
Simply ship. Every time.
http://release-approaches.com/
DevOps involves development and operations engineers working together throughout the entire lifecycle of a service, from design to production support. This breaks down the traditional silos between development and operations teams. The document discusses DevOps practices like continuous integration, infrastructure as code, monitoring and metrics, and implementing processes to minimize the impact of disruptions and outages. It emphasizes adopting DevOps culture from the start and evolving practices over time in a way that makes sense for the business.
This document discusses lessons learned around crisis communication at VictorOps. It provides tips for establishing a cross-functional crisis communication process that includes agreeing on when and how often to communicate, what gets communicated, who manages the message, and where the message is shared. The goal is to control the messaging and build trust with users during times of crisis. An effective crisis communication process can help manage reputational impact and make communicating less burdensome when incidents occur.
- Real-life stories of blameless post-mortems in action
- An understanding of why blaming members of a team for an outage or issue is counter productive
- Actionable steps to help you perform post-mortems in a blameless manner.
Puppet Camp Portland: Nagios Management With Puppet (Beginner)Puppet
This document discusses managing Nagios monitoring with Puppet. It describes key Puppet features like exported resources, Hiera, templates and Facter that help avoid monitoring gaps, keep configs consistent, and learn Puppet. It provides examples of using these features to define Nagios hosts, services and configs dynamically based on variables. While existing Nagios modules exist, the author wanted one that automatically adds/removes hosts and uses host/service groups. The full implementation combines Hiera, templates, facts and exported resources to dynamically build configs.
The Unrealized Role of Monitoring & Alerting w/ Jason HandSonatype
In today’s world, a company must be a “Learning Organization” in order to be successful and innovative. Learning from both failure and success, in order to implement small incremental improvements is critical. But until you implement and apply new information, you haven’t truly “learned” anything and you certainly haven’t improved.
According to the 2015 Monitoring Survey, most companies leverage metrics from monitoring and logging purely for performance analytics and trending. If high availability and reliability are important, they also leverage metrics to alert on fault and anomaly detection. Despite these “best practices”, the metrics are primarily only used as context to keep things “running” or return them back to “normal” if there’s a problem. Rarely is that data used as a method to identify areas of improvement once services have been restored. When an outage occurs to your system, you will absolutely repair and restore services as best you know how, but are you paying attention to the data from the recovery efforts? What were operators seeing during diagnosis and remediation? What were their actions? What was going on with everyone, including conversations? A step-by-step replay of exactly what took place during that outage.
This “old-view” perspective on the purpose of monitoring, logging, and alerting leaves the full value of metrics unrealized. It fails to address what’s important to the overall business objective and it lacks any hope of seeking out innovation or disruption of the status quo.
This talk will illustrate how to identify if your company is making the best use of metrics and ways to not only learn from failure, but to become a “Learning Company”.
Icinga Camp San Diego 2016 - Unrealized Role of MonitoringIcinga
The document discusses the unrealized role of monitoring and alerting in driving learning, innovation, and continuous improvement. It argues that underutilizing monitoring data prevents organizations from learning from their experiences with failures and successes. By continually understanding events and responses over time through monitoring, organizations can take actions that lead to resilient systems and high availability. The key is shifting focus from just maintaining systems to also improving and innovating based on lessons learned.
Failure as Success Devops Roadtrip Seattle 2016VictorOps
'Failure' as 'Success': The Mindset, Methods, and Landmines
J. Paul Reed
Release Engineering Approaches
Simply ship. Every time.
http://release-approaches.com/
DevOps involves development and operations engineers working together throughout the entire lifecycle of a service, from design to production support. This breaks down the traditional silos between development and operations teams. The document discusses DevOps practices like continuous integration, infrastructure as code, monitoring and metrics, and implementing processes to minimize the impact of disruptions and outages. It emphasizes adopting DevOps culture from the start and evolving practices over time in a way that makes sense for the business.
This document discusses lessons learned around crisis communication at VictorOps. It provides tips for establishing a cross-functional crisis communication process that includes agreeing on when and how often to communicate, what gets communicated, who manages the message, and where the message is shared. The goal is to control the messaging and build trust with users during times of crisis. An effective crisis communication process can help manage reputational impact and make communicating less burdensome when incidents occur.
Move past the jargon. See how DevOps plays into incident management and resolution.
Join guest Forrester Analysts and experts from local Colorado companies for a ½ day event focused on the latest and greatest DevOps practices for those tasked with maintaining uptime.
The document discusses the results of a study on the effects of exercise on memory and thinking abilities in older adults. The study found that regular exercise can help reduce the decline in thinking abilities that often occurs with age. Older adults who exercised regularly performed better on cognitive tests and brain scans showed they had greater activity in important areas for memory and learning compared to less active peers.
Dealing with an outage is so much more than just getting notified that a server is down. From alerting to resolution, learn more about the incident lifecycle and how each phase contributes to MTTR.
Jason Hand, DevOps Evangelist at VictorOps, and Michael Ansel, from Box, explain what ChatOps is, how it can help different teams in your organization, and where security comes into play. You'll learn tips to get started, tools needed and emerging best practices around the topic.
DevOps represents cultural change. Whether it’s the change of resistant engineers that don’t want to be on-call or the change of Operations teams to have more empathy towards their counterparts writing code, to the willingness of executives to embrace a culture of automation, measurement and sharing. Organizations must overcome the culture war to be able to approach the agility and productivity that organizations following a DevOps model gain. The faster they can get there, the faster these organizations can take the competitive edge away from traditional enterprises.
Resolving an incident can be a complex process that takes a lot of time and many people. According to the 2014 State of On-call Report, most teams report that it take 10-30 minutes to resolve an incident on average, 5 people are needed to help with resolution.
But it doesn't have to be that way. Jason Hand presents best practices and tips for surviving every stage of the firefight - from when an alert comes in to pulling reports after its over.
Clusters are getting bigger and bigger and machines are getting more and more powerful and yet we continue to use architectures that worked for websites built during the 90’s internet scale. Microservices vs. Monoliths glosses over a key architectural distinction in the way we build concurrency into our applications. We’ll define terms like concurrency and parallelism and learn how the key question in an architecture is message passing vs. shared mutable state. We’ll also look at concepts like Actors and CSP for creating a holistic messaging passing architecture that will let you truly scale your architecture.
An Introduction to Rearview - Time Series Based MonitoringVictorOps
Jeff Simpson, senior software engineer at VictorOps, delivered this presentation at the Frontrange Alerting & Monitoring meetup...along with an awesome live demo.
Putting Devs On-Call: How to Empower Your TeamVictorOps
A main tenet of DevOps is bridging the gap between the Dev team and the Ops team. One way to accomplish this is to include devs in the on-call rotation. While this may sound difficult, it’s not impossible to do…as our guide demonstrates.
We profile four companies that have successfully transitioned their dev team to being on-call and their stories can provide examples for how you too can do it.
Join DevOps Evangelist, Jason Hand, for a discussion on ChatOps and the movement to deploy, measure, and mitigate from a chat client.
With more and more teams implementing methods to trigger commands from within their favorite chat clients, the time it takes to perform specific and repetitive tasks has been dramatically reduced. In providing a real-time command history to others, we can share knowledge and learn from each other faster than ever before.
Everyone knows the importance of post-mortems but something seems to be keeping your team from actually doing them. Whether it’s a question of psychology or sociology, our guide provides six reasons why your post-mortem process might be failing. Read more to see how you can stop making these mistakes!
This document provides tips and strategies for surviving and being effective while on-call as an IT professional. It discusses preparing for being on-call by correctly configuring alerts and escalation policies. It emphasizes the importance of having a handoff meeting and buddy system to collaborate with others. During a crisis, it recommends keeping a clear head, calling in additional support from the team as needed, and fostering a blame-free culture for problem solving. It also suggests following up after an incident with a post-mortem to document lessons learned.
Blameless Post-mortems: Everything You Ever Wanted to KnowVictorOps
This document discusses the importance of conducting post-mortems, or reviews of incidents like outages, in order to learn from mistakes and improve processes. Post-mortems are meetings where stakeholders discuss what happened during an incident, what worked and what didn't, to collect information and reduce the impact of future incidents. They provide benefits like organizational learning, improved estimating and scheduling, continuous improvement, and team building. Creating an open and blame-free environment is key for effective post-mortems. Checklists and documentation of timelines, remediation plans, and conversations can help make post-mortem reviews actionable.
VictorOps Guide to Blameless Post-mortemsVictorOps
This document provides guidance on how to conduct blameless post-mortems after a system outage or failure. It emphasizes that post-mortems should focus on learning rather than blame, and outlines 5 key steps: 1) set the context by explaining the purpose is to learn without blame, 2) build a timeline of events, 3) determine and prioritize remedies, 4) publish findings widely, and 5) ask questions to understand various perspectives without punishment. The overall goal is to improve systems and processes by understanding failures from the viewpoints of those involved, without fear of retribution.
The Microsoft 365 Migration Tutorial For Beginner.pptxoperationspcvita
This presentation will help you understand the power of Microsoft 365. However, we have mentioned every productivity app included in Office 365. Additionally, we have suggested the migration situation related to Office 365 and how we can help you.
You can also read: https://www.systoolsgroup.com/updates/office-365-tenant-to-tenant-migration-step-by-step-complete-guide/
Essentials of Automations: Exploring Attributes & Automation ParametersSafe Software
Building automations in FME Flow can save time, money, and help businesses scale by eliminating data silos and providing data to stakeholders in real-time. One essential component to orchestrating complex automations is the use of attributes & automation parameters (both formerly known as “keys”). In fact, it’s unlikely you’ll ever build an Automation without using these components, but what exactly are they?
Attributes & automation parameters enable the automation author to pass data values from one automation component to the next. During this webinar, our FME Flow Specialists will cover leveraging the three types of these output attributes & parameters in FME Flow: Event, Custom, and Automation. As a bonus, they’ll also be making use of the Split-Merge Block functionality.
You’ll leave this webinar with a better understanding of how to maximize the potential of automations by making use of attributes & automation parameters, with the ultimate goal of setting your enterprise integration workflows up on autopilot.
Discover top-tier mobile app development services, offering innovative solutions for iOS and Android. Enhance your business with custom, user-friendly mobile applications.
Move past the jargon. See how DevOps plays into incident management and resolution.
Join guest Forrester Analysts and experts from local Colorado companies for a ½ day event focused on the latest and greatest DevOps practices for those tasked with maintaining uptime.
The document discusses the results of a study on the effects of exercise on memory and thinking abilities in older adults. The study found that regular exercise can help reduce the decline in thinking abilities that often occurs with age. Older adults who exercised regularly performed better on cognitive tests and brain scans showed they had greater activity in important areas for memory and learning compared to less active peers.
Dealing with an outage is so much more than just getting notified that a server is down. From alerting to resolution, learn more about the incident lifecycle and how each phase contributes to MTTR.
Jason Hand, DevOps Evangelist at VictorOps, and Michael Ansel, from Box, explain what ChatOps is, how it can help different teams in your organization, and where security comes into play. You'll learn tips to get started, tools needed and emerging best practices around the topic.
DevOps represents cultural change. Whether it’s the change of resistant engineers that don’t want to be on-call or the change of Operations teams to have more empathy towards their counterparts writing code, to the willingness of executives to embrace a culture of automation, measurement and sharing. Organizations must overcome the culture war to be able to approach the agility and productivity that organizations following a DevOps model gain. The faster they can get there, the faster these organizations can take the competitive edge away from traditional enterprises.
Resolving an incident can be a complex process that takes a lot of time and many people. According to the 2014 State of On-call Report, most teams report that it take 10-30 minutes to resolve an incident on average, 5 people are needed to help with resolution.
But it doesn't have to be that way. Jason Hand presents best practices and tips for surviving every stage of the firefight - from when an alert comes in to pulling reports after its over.
Clusters are getting bigger and bigger and machines are getting more and more powerful and yet we continue to use architectures that worked for websites built during the 90’s internet scale. Microservices vs. Monoliths glosses over a key architectural distinction in the way we build concurrency into our applications. We’ll define terms like concurrency and parallelism and learn how the key question in an architecture is message passing vs. shared mutable state. We’ll also look at concepts like Actors and CSP for creating a holistic messaging passing architecture that will let you truly scale your architecture.
An Introduction to Rearview - Time Series Based MonitoringVictorOps
Jeff Simpson, senior software engineer at VictorOps, delivered this presentation at the Frontrange Alerting & Monitoring meetup...along with an awesome live demo.
Putting Devs On-Call: How to Empower Your TeamVictorOps
A main tenet of DevOps is bridging the gap between the Dev team and the Ops team. One way to accomplish this is to include devs in the on-call rotation. While this may sound difficult, it’s not impossible to do…as our guide demonstrates.
We profile four companies that have successfully transitioned their dev team to being on-call and their stories can provide examples for how you too can do it.
Join DevOps Evangelist, Jason Hand, for a discussion on ChatOps and the movement to deploy, measure, and mitigate from a chat client.
With more and more teams implementing methods to trigger commands from within their favorite chat clients, the time it takes to perform specific and repetitive tasks has been dramatically reduced. In providing a real-time command history to others, we can share knowledge and learn from each other faster than ever before.
Everyone knows the importance of post-mortems but something seems to be keeping your team from actually doing them. Whether it’s a question of psychology or sociology, our guide provides six reasons why your post-mortem process might be failing. Read more to see how you can stop making these mistakes!
This document provides tips and strategies for surviving and being effective while on-call as an IT professional. It discusses preparing for being on-call by correctly configuring alerts and escalation policies. It emphasizes the importance of having a handoff meeting and buddy system to collaborate with others. During a crisis, it recommends keeping a clear head, calling in additional support from the team as needed, and fostering a blame-free culture for problem solving. It also suggests following up after an incident with a post-mortem to document lessons learned.
Blameless Post-mortems: Everything You Ever Wanted to KnowVictorOps
This document discusses the importance of conducting post-mortems, or reviews of incidents like outages, in order to learn from mistakes and improve processes. Post-mortems are meetings where stakeholders discuss what happened during an incident, what worked and what didn't, to collect information and reduce the impact of future incidents. They provide benefits like organizational learning, improved estimating and scheduling, continuous improvement, and team building. Creating an open and blame-free environment is key for effective post-mortems. Checklists and documentation of timelines, remediation plans, and conversations can help make post-mortem reviews actionable.
VictorOps Guide to Blameless Post-mortemsVictorOps
This document provides guidance on how to conduct blameless post-mortems after a system outage or failure. It emphasizes that post-mortems should focus on learning rather than blame, and outlines 5 key steps: 1) set the context by explaining the purpose is to learn without blame, 2) build a timeline of events, 3) determine and prioritize remedies, 4) publish findings widely, and 5) ask questions to understand various perspectives without punishment. The overall goal is to improve systems and processes by understanding failures from the viewpoints of those involved, without fear of retribution.
The Microsoft 365 Migration Tutorial For Beginner.pptxoperationspcvita
This presentation will help you understand the power of Microsoft 365. However, we have mentioned every productivity app included in Office 365. Additionally, we have suggested the migration situation related to Office 365 and how we can help you.
You can also read: https://www.systoolsgroup.com/updates/office-365-tenant-to-tenant-migration-step-by-step-complete-guide/
Essentials of Automations: Exploring Attributes & Automation ParametersSafe Software
Building automations in FME Flow can save time, money, and help businesses scale by eliminating data silos and providing data to stakeholders in real-time. One essential component to orchestrating complex automations is the use of attributes & automation parameters (both formerly known as “keys”). In fact, it’s unlikely you’ll ever build an Automation without using these components, but what exactly are they?
Attributes & automation parameters enable the automation author to pass data values from one automation component to the next. During this webinar, our FME Flow Specialists will cover leveraging the three types of these output attributes & parameters in FME Flow: Event, Custom, and Automation. As a bonus, they’ll also be making use of the Split-Merge Block functionality.
You’ll leave this webinar with a better understanding of how to maximize the potential of automations by making use of attributes & automation parameters, with the ultimate goal of setting your enterprise integration workflows up on autopilot.
Discover top-tier mobile app development services, offering innovative solutions for iOS and Android. Enhance your business with custom, user-friendly mobile applications.
HCL Notes und Domino Lizenzkostenreduzierung in der Welt von DLAUpanagenda
Webinar Recording: https://www.panagenda.com/webinars/hcl-notes-und-domino-lizenzkostenreduzierung-in-der-welt-von-dlau/
DLAU und die Lizenzen nach dem CCB- und CCX-Modell sind für viele in der HCL-Community seit letztem Jahr ein heißes Thema. Als Notes- oder Domino-Kunde haben Sie vielleicht mit unerwartet hohen Benutzerzahlen und Lizenzgebühren zu kämpfen. Sie fragen sich vielleicht, wie diese neue Art der Lizenzierung funktioniert und welchen Nutzen sie Ihnen bringt. Vor allem wollen Sie sicherlich Ihr Budget einhalten und Kosten sparen, wo immer möglich. Das verstehen wir und wir möchten Ihnen dabei helfen!
Wir erklären Ihnen, wie Sie häufige Konfigurationsprobleme lösen können, die dazu führen können, dass mehr Benutzer gezählt werden als nötig, und wie Sie überflüssige oder ungenutzte Konten identifizieren und entfernen können, um Geld zu sparen. Es gibt auch einige Ansätze, die zu unnötigen Ausgaben führen können, z. B. wenn ein Personendokument anstelle eines Mail-Ins für geteilte Mailboxen verwendet wird. Wir zeigen Ihnen solche Fälle und deren Lösungen. Und natürlich erklären wir Ihnen das neue Lizenzmodell.
Nehmen Sie an diesem Webinar teil, bei dem HCL-Ambassador Marc Thomas und Gastredner Franz Walder Ihnen diese neue Welt näherbringen. Es vermittelt Ihnen die Tools und das Know-how, um den Überblick zu bewahren. Sie werden in der Lage sein, Ihre Kosten durch eine optimierte Domino-Konfiguration zu reduzieren und auch in Zukunft gering zu halten.
Diese Themen werden behandelt
- Reduzierung der Lizenzkosten durch Auffinden und Beheben von Fehlkonfigurationen und überflüssigen Konten
- Wie funktionieren CCB- und CCX-Lizenzen wirklich?
- Verstehen des DLAU-Tools und wie man es am besten nutzt
- Tipps für häufige Problembereiche, wie z. B. Team-Postfächer, Funktions-/Testbenutzer usw.
- Praxisbeispiele und Best Practices zum sofortigen Umsetzen
"Choosing proper type of scaling", Olena SyrotaFwdays
Imagine an IoT processing system that is already quite mature and production-ready and for which client coverage is growing and scaling and performance aspects are life and death questions. The system has Redis, MongoDB, and stream processing based on ksqldb. In this talk, firstly, we will analyze scaling approaches and then select the proper ones for our system.
Generating privacy-protected synthetic data using Secludy and MilvusZilliz
During this demo, the founders of Secludy will demonstrate how their system utilizes Milvus to store and manipulate embeddings for generating privacy-protected synthetic data. Their approach not only maintains the confidentiality of the original data but also enhances the utility and scalability of LLMs under privacy constraints. Attendees, including machine learning engineers, data scientists, and data managers, will witness first-hand how Secludy's integration with Milvus empowers organizations to harness the power of LLMs securely and efficiently.
How to Interpret Trends in the Kalyan Rajdhani Mix Chart.pdfChart Kalyan
A Mix Chart displays historical data of numbers in a graphical or tabular form. The Kalyan Rajdhani Mix Chart specifically shows the results of a sequence of numbers over different periods.
Main news related to the CCS TSI 2023 (2023/1695)Jakub Marek
An English 🇬🇧 translation of a presentation to the speech I gave about the main changes brought by CCS TSI 2023 at the biggest Czech conference on Communications and signalling systems on Railways, which was held in Clarion Hotel Olomouc from 7th to 9th November 2023 (konferenceszt.cz). Attended by around 500 participants and 200 on-line followers.
The original Czech 🇨🇿 version of the presentation can be found here: https://www.slideshare.net/slideshow/hlavni-novinky-souvisejici-s-ccs-tsi-2023-2023-1695/269688092 .
The videorecording (in Czech) from the presentation is available here: https://youtu.be/WzjJWm4IyPk?si=SImb06tuXGb30BEH .
Monitoring and Managing Anomaly Detection on OpenShift.pdfTosin Akinosho
Monitoring and Managing Anomaly Detection on OpenShift
Overview
Dive into the world of anomaly detection on edge devices with our comprehensive hands-on tutorial. This SlideShare presentation will guide you through the entire process, from data collection and model training to edge deployment and real-time monitoring. Perfect for those looking to implement robust anomaly detection systems on resource-constrained IoT/edge devices.
Key Topics Covered
1. Introduction to Anomaly Detection
- Understand the fundamentals of anomaly detection and its importance in identifying unusual behavior or failures in systems.
2. Understanding Edge (IoT)
- Learn about edge computing and IoT, and how they enable real-time data processing and decision-making at the source.
3. What is ArgoCD?
- Discover ArgoCD, a declarative, GitOps continuous delivery tool for Kubernetes, and its role in deploying applications on edge devices.
4. Deployment Using ArgoCD for Edge Devices
- Step-by-step guide on deploying anomaly detection models on edge devices using ArgoCD.
5. Introduction to Apache Kafka and S3
- Explore Apache Kafka for real-time data streaming and Amazon S3 for scalable storage solutions.
6. Viewing Kafka Messages in the Data Lake
- Learn how to view and analyze Kafka messages stored in a data lake for better insights.
7. What is Prometheus?
- Get to know Prometheus, an open-source monitoring and alerting toolkit, and its application in monitoring edge devices.
8. Monitoring Application Metrics with Prometheus
- Detailed instructions on setting up Prometheus to monitor the performance and health of your anomaly detection system.
9. What is Camel K?
- Introduction to Camel K, a lightweight integration framework built on Apache Camel, designed for Kubernetes.
10. Configuring Camel K Integrations for Data Pipelines
- Learn how to configure Camel K for seamless data pipeline integrations in your anomaly detection workflow.
11. What is a Jupyter Notebook?
- Overview of Jupyter Notebooks, an open-source web application for creating and sharing documents with live code, equations, visualizations, and narrative text.
12. Jupyter Notebooks with Code Examples
- Hands-on examples and code snippets in Jupyter Notebooks to help you implement and test anomaly detection models.
Have you ever been confused by the myriad of choices offered by AWS for hosting a website or an API?
Lambda, Elastic Beanstalk, Lightsail, Amplify, S3 (and more!) can each host websites + APIs. But which one should we choose?
Which one is cheapest? Which one is fastest? Which one will scale to meet our needs?
Join me in this session as we dive into each AWS hosting service to determine which one is best for your scenario and explain why!
What is an RPA CoE? Session 1 – CoE VisionDianaGray10
In the first session, we will review the organization's vision and how this has an impact on the COE Structure.
Topics covered:
• The role of a steering committee
• How do the organization’s priorities determine CoE Structure?
Speaker:
Chris Bolin, Senior Intelligent Automation Architect Anika Systems
Taking AI to the Next Level in Manufacturing.pdfssuserfac0301
Read Taking AI to the Next Level in Manufacturing to gain insights on AI adoption in the manufacturing industry, such as:
1. How quickly AI is being implemented in manufacturing.
2. Which barriers stand in the way of AI adoption.
3. How data quality and governance form the backbone of AI.
4. Organizational processes and structures that may inhibit effective AI adoption.
6. Ideas and approaches to help build your organization's AI strategy.
zkStudyClub - LatticeFold: A Lattice-based Folding Scheme and its Application...Alex Pruden
Folding is a recent technique for building efficient recursive SNARKs. Several elegant folding protocols have been proposed, such as Nova, Supernova, Hypernova, Protostar, and others. However, all of them rely on an additively homomorphic commitment scheme based on discrete log, and are therefore not post-quantum secure. In this work we present LatticeFold, the first lattice-based folding protocol based on the Module SIS problem. This folding protocol naturally leads to an efficient recursive lattice-based SNARK and an efficient PCD scheme. LatticeFold supports folding low-degree relations, such as R1CS, as well as high-degree relations, such as CCS. The key challenge is to construct a secure folding protocol that works with the Ajtai commitment scheme. The difficulty, is ensuring that extracted witnesses are low norm through many rounds of folding. We present a novel technique using the sumcheck protocol to ensure that extracted witnesses are always low norm no matter how many rounds of folding are used. Our evaluation of the final proof system suggests that it is as performant as Hypernova, while providing post-quantum security.
Paper Link: https://eprint.iacr.org/2024/257
AppSec PNW: Android and iOS Application Security with MobSFAjin Abraham
Mobile Security Framework - MobSF is a free and open source automated mobile application security testing environment designed to help security engineers, researchers, developers, and penetration testers to identify security vulnerabilities, malicious behaviours and privacy concerns in mobile applications using static and dynamic analysis. It supports all the popular mobile application binaries and source code formats built for Android and iOS devices. In addition to automated security assessment, it also offers an interactive testing environment to build and execute scenario based test/fuzz cases against the application.
This talk covers:
Using MobSF for static analysis of mobile applications.
Interactive dynamic security assessment of Android and iOS applications.
Solving Mobile app CTF challenges.
Reverse engineering and runtime analysis of Mobile malware.
How to shift left and integrate MobSF/mobsfscan SAST and DAST in your build pipeline.
10. By clicking on Settings, you’ll see a
button for Integrations on the top of
the page.
All of our available integrations are
listed there. Look for Raygun under
REST endpoint options.
VO overview: whether on the web app or mobile app, you’ll get the full picture of what’s happening in your infrastructure, with the context of what’s happened, who has Acked the issue and what other team members are saying about the incident.
Transmog allows the on-call engineers to have the solution they need, right when they need it. Annotating alerts can help reduce TTR and the alert fatigue caused by an influx of unactionable alerts.
Definition of the problem that our integration solves…
Daniel to talk about Raygun side of integration
Screenshots of integration
Screenshots of integration
Screenshots of integration
Raygun high-level overview
Summary slide – conclusion, seed questions and contact info