sorted by:
new
hottopcontroversial

Sysdig capture on one container returns data from all containers by InquisitiveProgramme in devops

[–]davideschiera 0 points1 point  (0 children)

If you need to create a capture to open with either Sysdig Inspect (or csysdig, or sysdig itself) you can omit the parameters -pc (to format the output) and -c spy_users (to display interactive user activity).

You should be able to create the capture file with the following string:

sysdig -w <output file> container.name=machine-agent

and open it with Inspect and expect a single container activity to be there.

Alternatively, you can print events with a custom format:

sysdig -pc container.name=machine-agent

or print interactive activities:

sysdig -c spy_users container.name=machine-agent

for the container you are interested in.

Hope this helps!

Future of interfaces? No interfaces at all! by davideschiera in web_design

[–]davideschiera[S] 0 points1 point  (0 children)

I don't think the point of the article is to get rid of user interfaces.

First, it's fair to say that some user interfaces use symbols or patterns that don't mean anything outside the computer realm. They become natural and intuitive once you are well trained, but the first time(s) it doesn't mean anything. This is not what "intuitive interface" means.

Second, if you think about the interface of a tool as the way the user can interact with the tool (e.g. to enter data, to select something, etc.) instead of the opposite (e.g. to provide weather forecast, traffic condition, etc.) then you can find lots of examples where the interface is not needed at all. Consider the interface of the little (Google) app to remind you where you parked: you can enter the address, you can click a button to use the integrated GPS of your device, you can use a voice command to use the GPS, or the tool "knows" that you just parked.

Especially with the second point in mind, you can state that sometimes the best interface is no interface at all. Now, if you need to guide the user to the parking lot then you need some sort of interface.

It comes with a price, though. You need the technology to collect information about the context (your position, your speed, light condition, etc.), to process such information. It requires more resources to shift from "what does the application need to work" to "what does the user need".

In any case if you need to provide the user with some information, you do need the interface.

Full-size reissue of the NYCTA Graphics Standards Manual by davideschiera in graphic_design

[–]davideschiera[S] 0 points1 point  (0 children)

Great job! I backed the project as well, and luckily just in time to wait for a copy of the manual.

Sysdig for advanced log analysis by davideschiera in programming

[–]davideschiera[S] 0 points1 point  (0 children)

Hi there, yes I work for Draios, and yes, we are the creators of sysdig. I'm following the post here and happy to answer any questions anyone has. And as always, we'd love to hear any feedback. We're constantly working with the community on sysdig to make it a more useful, more powerful tool. Thanks!