The pandemic has changed the way teams collaborate within an organization and between companies. With work from home becoming the new normal, employees are turning to new options for collaboration, meeting, training and onboarding have moved online. The office is now a virtual space. With the increasing demand for online meetings, it is even more important to monitor the health and performance of such meetings.
The new release of FortiOS 6.4 from 31 March 2020 brings a new and interesting feature of using webhooks for external API calls and enable automation stitches, which are easy to configure in FortiGate UI and allow you to run multiple actions. This led us to revise our integration script to utilize this functionality and allow administrators to easily configure different levels of mitigation with the webhooks.
When monitoring third-party applications with Prometheus, you’ll need an exporter if the application doesn’t already expose metrics in the appropriate format. How do you find an appropriate exporter, and once you have your exporters, how should you organize your label taxonomies to reflect your infrastructure? Many applications in the systems you’re in charge of will be third-party applications, which do not natively expose Prometheus-formatted metrics.
You know the feeling. You’ve just deployed a new version to production and are monitoring the Rollbar dashboard for any new errors or looking out for any Slack notifications. You’re keeping an eye on the number of new or reactivated errors, their severity level, and triaging to see which errors need to be assigned and to whom. Now what if you could automate these tasks?
When it comes to troubleshooting application performance, metrics are no longer enough. To fully understand the environment you need logs and traces. Today, we’re going to focus on your Java applications.
Our sources state that there has been a 20% increase in web-skimming attacks since the outbreak of the COVID-19 virus. Recently, we have witnessed some high-profile Magecart attacks on websites which have gained popularity during the pandemic, including fitness-based websites. The latest fitness-based website attack reported is YogaFit, who were compromised for over 6 weeks.
Troubleshoot your IP addresses and switch ports faster and smarter! Managing and troubleshooting your network IPs and ports effectively can become difficult if hands-on network monitoring by your IT team is required at all times. Ever wondered if you can monitor your IPs and endpoints on the go? If yes, the solution you need is the OpUtils mobile app.
Last week we released Telegraf 1.15 with new plugins for network monitoring and a large number of processors to help with your data ingestion. All packages were written in Go 1.14.5. This all couldn’t have been done without the 50+ community members who contributed to writing plugins, fixing bugs, reviewing code, and everything else to help make Telegraf better! Here’s a quick look into new plugins and features we launched in Telegraf 1.15.
Our Telegraf Starlark Processor Plugin is an exciting new processor in Telegraf 1.15 that gives you the flexibility of performing various operations in Telegraf using the Starlark language. What is Starlark, you ask? Starlark (formerly known as Skylark) is a language intended for use as a configuration language. Starlark is a dialect of Python. Like Python, it is a dynamically typed language with high-level data types, first-class functions with lexical scope, and garbage collection.
