5. Tenant API
• Tenant = {Host, Event Producer, Profile}
• A Tenant = A Consumer
• Event Producer = APP or Service
• Profile = [Event Producer, …]
• Host = Node , link to a profile(1:1)
6. Tenant API
• Requests to coordinator worker
• Tenant, Host, Event Producer, Profile
=> CRUD Available
• has a TOKEN
=> validate, reset a token
7. Correlator API
• Requests
To a Correlator worker server
From a Consumer server
via http(s)
with a Message token(Tenant token)
• Stores a collection named “logs” in Mongo
8. Coordinator API
• Pairing
- registers a worker
• Configuration
– requests a worker’s configuration
• Status
– updates a workers status
9. Status API
• Worker Status API (PUT, Manually)
- System Load Average
- Disk Usage
• Coordinator Status API
- grid status
- individual worker status
10. Broadcaster API
• What’s Brodcaster API?
I don’t know well!
• Communicates with coordinator worker
server.
• New Feature!
24. Conclusion
• Well-made backend APIs for logging
(Good architecture)
• Distributed workers processing
• Diverse Persona(worker)
• In early development
• Nobody in its community
(Stack Overflow, Google Groups)
25. Not yet
• Data Store – Only MongoDB
Hadoop / HDFS / Hbase
Elastic Search
• Perfect documentation
need more examples
need exact examples
26. The thing we can now do with meniscus is
JUST to create log data into mongodb via
restful api and to fetch log data from
mongodb.