Running Argus in production means aggregating data of one or several live networks. Much of this data is sensitive and should not be exposed to third-party viewers.
We want more people and institutions to adapt and use Argus to monitor their networks. To achieve this, we want to show them how Argus works. However, it is impossible to use production data in a demo for aforementioned reasons, so video-demos became a fallback for the time being.
Still, an option to live demo Argus' functionality without exposing sensitive data would be stellar!
Objective
Create a mechanism to insert "mock incidents" and events into a new Argus instance, so Argus and Argus-frontend can be live-demoed safely to third-party viewers.
Specs and nice-to-haves
Starting point is always a freshly-setup, plain Argus instance.
The mechanism should create fake incidents with as little user interaction as possible.
The mechanism is run before the demo, and maybe also during (see below).
Incidents and events should be "semi-realistic". This means: They should be as realistic as possible without being too "close" to reality.
A bit of research needed: Which data is considered sensitive in Uninett's context? (IP-Adresses, customer names, etc.) + come up with a good way to "fake" each. Don't be afraid to use your imagination, lists of examples, and add some randomness :)
Not just live data: Sometimes we want to fake hundreds of semi-realistic "older" incidents to just fill up the database.
Optional: A mechanism to insert an incident/event during the live demo, to show its immediate effects. (Convenient method to insert 1 new random incident at a user-defined time interval, for example. Or insert a new incident manually.)
Optional: Maybe also insert fake users, fake timeslot and fake ACKs?
Related issues and functions
open issues
https://github.com/Uninett/Argus/issues/150 is the closest open issue I could find. However, this issue is not about creating a demo site (= an Argus instance for demonstrating purposes), but a mechanism to fill a (short-lived) demo-instance with data ad hoc.
Motivation
Running Argus in production means aggregating data of one or several live networks. Much of this data is sensitive and should not be exposed to third-party viewers.
We want more people and institutions to adapt and use Argus to monitor their networks. To achieve this, we want to show them how Argus works. However, it is impossible to use production data in a demo for aforementioned reasons, so video-demos became a fallback for the time being. Still, an option to live demo Argus' functionality without exposing sensitive data would be stellar!
Objective
Create a mechanism to insert "mock incidents" and events into a new Argus instance, so Argus and Argus-frontend can be live-demoed safely to third-party viewers.
Specs and nice-to-haves
Related issues and functions
open issues
https://github.com/Uninett/Argus/issues/150 is the closest open issue I could find. However, this issue is not about creating a demo site (= an Argus instance for demonstrating purposes), but a mechanism to fill a (short-lived) demo-instance with data ad hoc.
closed issues
https://github.com/Uninett/Argus/issues/91 https://github.com/Uninett/Argus/issues/221
Argus methods
https://github.com/Uninett/Argus/blob/master/src/argus/dev/management/commands/create_fake_incident.py This method allows creating fake incidents in development.