Page History

...

• Simple static HTTP resource(s) that would be always/forever available (e.g. hosted at AWS?) to designate where the TIER collector(s) are

• Gliffy Diagram
  name grouperInstrumentation

  Note, we can start out with one collector.  Client failover is optional, the first endpoint might be used only for simple clients
• e.g. request: GET 

  • https://s3.amazonaws.com/

  tierdiscovery1

  • edu.internet2.tierinstrumentationcollector.

  edu/v1/collector  

  • discovery0/tierInstrumentationCollector_discovery.json

  ,

  • https://

  tierdiscovery2

  • s3-us-west-1.amazonaws.com/edu.internet2.tierinstrumentationcollector.

  edu/v1/collector

  • discovery1/tierInstrumentationCollector_discovery.json

{
  serviceEnabled: true,
  endpoints: [
    {
       uri: "https://tiercollector1grouperdemo.internet2.edu/tierInstrumentationCollector/tierInstrumentationCollector/v1/collectorupload"
    },
    {
       uri: "https://tiercollector2grouperdemo2.internet2.edu/tierInstrumentationCollector2/tierInstrumentationCollector/v1/collectorupload"
    }

  ]
}

Collector

• Simple REST endpoint that takes any name/value pairs in JSON in a simple structure of single valued strings
• The collector can just store each resource it gets and doesnt care what the attributes are, so the components can change their data as they need
• Of course the reporting and processing needs to take the attributes and values into account
• e.g. submission: POST https://tiercollector1.internet2.edu/v1/collector/dailyReport

...