Language Selection

English French German Italian Portuguese Spanish

HowTos

today's howtos

Filed under
HowTos

Leftovers: Software

Filed under
Software
HowTos
  • How Docker changes application monitoring

    As operations, IT, and engineering organizations coalesce around the value and importance of containers, they often ask the seemingly logical question: “How do I monitor Docker in my production environment?” As it turns out, this question has it backward. Monitoring the Docker daemon, the Kubernetes master, or the Mesos scheduler isn’t especially complicated, and there are, in fact, solutions for each of these.

    Running your applications in Docker containers only changes how the applications are packaged, scheduled, and orchestrated, not how they actually run. The question, properly rephrased, becomes, “How does Docker change how I monitor my applications?” As you might imagine, the answer to this question: “It depends.”

    The answer will be dictated by the dependencies of your environment and your use cases and objectives. The orchestration technology you use, the Docker image philosophy you follow, and the level of observability your containerized application provides, among other considerations, will all factor into how you monitor your applications.

    To begin to understand how a microservices regimen and a Dockerized environment will affect your monitoring strategy, ask yourself the following four simple questions. Note that the answers may differ for different applications, and your approach to monitoring should reflect these differences.

  • New libvirt website design
  • Spotify Windows, Mac, Linux desktop app: Update now to stop it trashing your SSD

    Music-streaming service Spotify has released an important update that stops its desktop client tearing into storage drives with massive and unnecessary write rates.

  • Alexa – Making that First Application Run
  • Shaggy Dogs and SpiderMonkey Unwinders
  • OVN Logical Flows and ovn-trace
  • Agile development w/ CI/CD – Automated cloud building & deployment (from scratch)
Syndicate content

More in Tux Machines

Security Leftovers

  • Someone is putting lots of work into hacking Github developers [Ed: Dan Goodin doesn't know that everything is under attack and cracking attempts just about all the time?]
    Open-source developers who use Github are in the cross-hairs of advanced malware that has steal passwords, download sensitive files, take screenshots, and self-destruct when necessary.
  • Security Orchestration and Incident Response
    Technology continues to advance, and this is all a changing target. Eventually, computers will become intelligent enough to replace people at real-time incident response. My guess, though, is that computers are not going to get there by collecting enough data to be certain. More likely, they'll develop the ability to exhibit understanding and operate in a world of uncertainty. That's a much harder goal. Yes, today, this is all science fiction. But it's not stupid science fiction, and it might become reality during the lifetimes of our children. Until then, we need people in the loop. Orchestration is a way to achieve that.

Leftover: Development (Linux)

  • Swan: Better Linux on Windows
    If you are a Linux user that has to use Windows — or even a Windows user that needs some Linux support — Cygwin has long been a great tool for getting things done. It provides a nearly complete Linux toolset. It also provides almost the entire Linux API, so that anything it doesn’t supply can probably be built from source. You can even write code on Windows, compile and test it and (usually) port it over to Linux painlessly.
  • Lint for Shell Scripters
    It used to be one of the joys of writing embedded software was never having to deploy shell scripts. But now with platforms like the Raspberry Pi becoming very common, Linux shell scripts can be a big part of a system–even the whole system, in some cases. How do you know your shell script is error-free before you deploy it? Of course, nothing can catch all errors, but you might try ShellCheck.
  • Android: Enabling mainline graphics
    Android uses the HWC API to communicate with graphics hardware. This API is not supported on the mainline Linux graphics stack, but by using drm_hwcomposer as a shim it now is. The HWC (Hardware Composer) API is used by SurfaceFlinger for compositing layers to the screen. The HWC abstracts objects such as overlays and 2D blitters and helps offload some work that would normally be done with OpenGL. SurfaceFlinger on the other hand accepts buffers from multiple sources, composites them, and sends them to the display.
  • Collabora's Devs Make Android's HWC API Work in Mainline Linux Graphics Stack
    Collabora's Mark Filion informs Softpedia today about the latest work done by various Collabora developers in collaboration with Google's ChromeOS team to enable mainline graphics on Android. The latest blog post published by Collabora's Robert Foss reveals the fact that both team managed to develop a shim called drm_hwcomposer, which should enable Android's HWC (Hardware Composer) API to communicate with the graphics hardware, including Android 7.0's version 2 HWC API.

today's howtos

Reports From and About Cloud Native Computing Foundation (CNCF)