In order to save graphs under 'My Graphs' and 'User Graphs' you simply need to log into Graphite and the Save/Delete buttons will then appear on the top of the Composer window. To log in you need to either create an account for yourself in the Django database or setup LDAP authentication. LDAP authentication is setup through local_settings.py, check out the example file's comments for details on doing that (or just ask if you run into any issues). However if you're not using LDAP its pretty easy to create a local user in Django's database using the Django admin interface.
When you first installed Graphite there was a step where you had to initialize the database by running 'manage.py syncdb'. That prompted you to create an admin user, if you did that already you're good to go. Otherwise you need to create an admin user by running 'manage.py createsuperuser'.
Once your admin user is setup you can go to the django admin interface by visiting http://my-graphite-server/admin/ (note: the trailing slash is required!) and logging in as your admin user. From there you need to create a new user account by clicking 'Add' under the 'Users' section. After that, go back to the main Graphite page. You may need to logout if it thinks you're still the admin user. Then log back in as you're new user and you should be able to save graphs! Also once logged in you have the ability to set profile options. Currently there is only 1 option, the "advanced UI features" option. Enabling that puts a '*' element in every folder that has more than one element, making it easier to use wildcards when you build graphs.
Hope that helps.
-
https://answers.launchpad.net/graphite/+question/54887Bon ce code n'a pas marché chez moi... mais il faut bien garder en tête qu'une clé chargée avec un agent va résider en mémoire de manière non chiffrée ;)
Et de la même manière, elle va résider en mémoire sur un hôte distant si on se connecte en 'ssh -A'. Donc potentiellement, quelqu'un qui a un accès root sur cette machine distante peut récupérer les clés privés des gens qui s'y connectent (en -A)
github link via skunnyk
-
https://github.com/NetSPI/sshkey-grabAdd the directory, while ignoring all of the files it contains:
svn add -N [directory]
After adding the directory enter the directory and run the following command:
svn propset svn:ignore '*.*' .
Commit your changes:
svn commit -m "Added the directory and set the files within it to be ignored"
-
http://www.metaltoad.com/blog/adding-directory-subversion-and-ignoring-directory-contentsce serait plus simple avec tu partout
via sebsauvage
-
http://www.latimes.com/opinion/op-ed/la-og-bastile-vous-tu-20140711-htmlstory.htmlHMAC-based One-time Password : pour se faire l'équivalent d'un token rsa (genre securid) soi-même en utilisant son smartphone, c'est top et facile à mettre en place :)
-
http://sebsauvage.net/wiki/doku.php?id=totp&#codiadconf ops m6web bien cool!
sysdig
curl
graphite/statsd
collectd/sensu/seyren
ELK(Elasticsearch, Logstash, Kibana)
Elasticsearch :
jmeter/gatling
siege/wrk
tsung
gor
blitz.io, blazemater, neotys(saas)
via skunnyk
-
https://www.youtube.com/watch?v=O03GflHG-WU&feature=youtu.beC'est vrai que le Dockerfile est assez limité.. je pense que chef/puppet/xyz est nécessaire pour gérer un grand nombre de containers et surtout pour faciliter la maintenance et l'évolution de la configuration.
via skunnyk
-
http://www.getchef.com/blog/2014/07/15/release-chef-container-0-2-0-beta/
-
https://support.datastax.com/entries/43692547-Step-by-step-instructions-for-securing-JMX-authentication-for-nodetool-utility-OpsCenter-and-JConsolPas con du tout comme idée... mais niveau perf c'est impossible d'obtenir quelquechose de bien :D
-
https://github.com/philipl/pifs