DeployBoard / DeployBoard/deployboard-python
Admin Log
- Linguagem predominante
- Python
- Estrelas
- 10
- Forks
- 1
- Métricas de merge de PRs
- Nenhum PR com merge em 30d
Descrição
**Is your feature request related to a problem? Please describe.**
As an Admin, I would like a way to see user's historical usage. Similar to CloudTrail, I would like to log user activity into a collection in the database. What type of activity should be logged?
**Attempted Login** - success/failure at least. Do we want to log source IP address? We could potentially use this to notify the user they are logging in from a new IP address in case of unauthorized login.
**Page Loads** (I don't think we need to get this granular).
**Edit anything** - I think this is the most important piece. I'd like to know who changed what, and when. A lot of items already include the most recent change, it would be nice to be able to see a complete change history for that item.
**Delete anything** - If someone deletes something, they might delete the item from the collection, but it wouldn't delete the history from the log, so we can use this as a way to keep that data around.
**Describe the solution you'd like**
Similar to the logs collection for all the deployment information. We can have some type of activity logs collection that just holds all the Activity on the application as described above.
**Describe alternatives you've considered**
None.
**Additional context**
None.
Guia de contribuição
Nenhum guia de contribuição indexado para este repositório
Direção de pesquisa
Comece revisando a coleção de logs existente e o uso do banco de dados em deployboard-python. Esclareça quais atividades e campos devem ser mantidos antes de definir uma coleção de logs de atividades; considera-se concluído quando os administradores podem inspecionar o histórico de logins, edições e exclusões sem perder registros quando os itens são removidos.
Escrita pelo modelo de indexação a partir do texto da issue.
Avaliação
- Stack de tecnologia
- mongodb, python
- Domínio
- backend, databases, security
- Tipo de issue
- Funcionalidade
- Dificuldade
- 5/5
- Tempo estimado
- Mais de uma semana
- Status de atividade
- Estagnada
- Clareza
- Precisa de esclarecimento
- Facilidade para iniciantes
- 20/100