Revision history for AuditingDiscussions
No Differences
Additions:
- Latency from the monitoring host to the monitored host (can also set up monitoring agents, whos sole purpose is to feed data back to the monitor)
- DNS query response time
- DNS query response time
Deletions:
- DNS query response time
Additions:
- Latency from the monitoring host to the monitored host (can also set up monitoring agents, whos sole purpose is to feed data back to the monitor)
- DNS query response time
- DNS query response time
Deletions:
- DNS query response time
Deletions:
Additions:
=== Future Ideas ===
I have been playing with Centreon at work, and I have found the graphing features it offers very useful. This could be applied to the auditing infrastructure to supply graph statistics, of;
- Latency from the monitoring host to the monitored host (can also set up monitoring agents, whos sole purpose is to feed data back to the monitor)
- DNS query response time
Using SNMP with a unique community name which would be hard to guess could also help get remote host information easier.
I have been playing with Centreon at work, and I have found the graphing features it offers very useful. This could be applied to the auditing infrastructure to supply graph statistics, of;
- Latency from the monitoring host to the monitored host (can also set up monitoring agents, whos sole purpose is to feed data back to the monitor)
- DNS query response time
Using SNMP with a unique community name which would be hard to guess could also help get remote host information easier.
Additions:
~1) ++devise scheme for rsyncing configs, histories, etc.++
~1) ++prepare downloadable tarball and instructions for next host++
~1) ++prepare downloadable tarball and instructions for next host++
Deletions:
~1) prepare downloadable tarball and instructions for next host
Additions:
- Naming convention. for consistency with Hostmastering, .... mon1.pp.cc.opennic.glue where pp is province/state and cc is country
- We would like to consider/test a 'subversion (SVN)' system to keep revisions of the config files. Any ideas, recommendations? Who has this experience?
- We would like to consider/test a 'subversion (SVN)' system to keep revisions of the config files. Any ideas, recommendations? Who has this experience?
Deletions:
So the way this would work is, take the first 3 values of the City (Brisabane = BNE), then the country code (Australia = AU).
- Brought up on IRC by avo, we would like to use a subversion system to keep revisions of the config files. Any ideas, recommendations? Who has this experience?
Deletions:
Additions:
===Ideas to be discussed===
- Criteria for setting up a Monitoring Station
- Required MTA
- Pre-requisites (apache, ssh, etc)
- How to inform the audit team of a new Monitoring Station
- Email template that should be filled out when server established.
EXAMPLE
SERVER IP:
SERVER LOCATION (City, country):
SERVER ADMIN:
ADMINS EMAIL:
Upon submission of this, the Audit team will audit the new Monitoring Station, and when approved, a hostname will be given with the .glue tld.
- Naming convention. My thinking was this, bneau.opennic.glue, pausa.opennic.glue.
So the way this would work is, take the first 3 values of the City (Brisabane = BNE), then the country code (Australia = AU).
- Brought up on IRC by avo, we would like to use a subversion system to keep revisions of the config files. Any ideas, recommendations? Who has this experience?
- Criteria for setting up a Monitoring Station
- Required MTA
- Pre-requisites (apache, ssh, etc)
- How to inform the audit team of a new Monitoring Station
- Email template that should be filled out when server established.
EXAMPLE
SERVER IP:
SERVER LOCATION (City, country):
SERVER ADMIN:
ADMINS EMAIL:
Upon submission of this, the Audit team will audit the new Monitoring Station, and when approved, a hostname will be given with the .glue tld.
- Naming convention. My thinking was this, bneau.opennic.glue, pausa.opennic.glue.
So the way this would work is, take the first 3 values of the City (Brisabane = BNE), then the country code (Australia = AU).
- Brought up on IRC by avo, we would like to use a subversion system to keep revisions of the config files. Any ideas, recommendations? Who has this experience?
Additions:
~1) ++manually add Chris to the list of hosts++
~1) ++carefully review existing configs for monitoring and alerting++
~1) avo added the 3 monitors and modified hostgroups; all else looks good.
~1) ++carefully review existing configs for monitoring and alerting++
~1) avo added the 3 monitors and modified hostgroups; all else looks good.
Deletions:
~1) carefully review existing configs for monitoring and alerting
