active 2025-12-13 → 2025-12-27 (UTC)
Activity over time
Daily event counts in the loaded window
Line chart, 15 days from 2025-12-13 to 2025-12-27. Pushes: 6 total, peak 3 in a day. Pull requests: 0 total, peak 0 in a day. Issues: 24 total, peak 20 in a day. Comments: 13 total, peak 9 in a day. Stars: 0 total, peak 0 in a day.
- Pushes
- Pull requests
- Issues
- Comments
- Stars
Stars, PRs, issues and forks are under-captured in the later part of this window. GH Archive progressively stopped capturing non-push events during 2026 — −95% or worse by the end of the window. Every series here except Pushes fades for that reason, so a decline above reflects the archive, not this repository. Pushes stay reliable throughout, so read them, and the contributor counts derived from them, as the real signal. Data health has the measurements.
Top contributors
Pushes, PRs, issues, reviews and comments — stars and forks excluded, so this is contribution rather than popularity
| Contributor | Contributions | Pushes | PRs | Comments |
|---|---|---|---|---|
| JesusFSP | 43 | 6 | 0 | 13 |
Recent activity
Latest issues, pull requests and releases
- Issue#7JesusFSP2025-12-26 05:26Elaborar manual técnico con pasos de implementación y configuraciones.
- Issue comment#12JesusFSP2025-12-26 05:25Subir todo al repositorio del proyecto (/docs, /evidencias).
- Issue#9JesusFSP2025-12-26 05:22Capturar pruebas de carga con herramientas como curl, Postman o Pingdom.
- Issue comment#16JesusFSP2025-12-26 05:19Generar reporte de seguridad post-configuración.
- Issue comment#14JesusFSP2025-12-26 05:15Activar Azure Firewall o Application Gateway si aplica.
- Issue#18JesusFSP2025-12-26 05:11Configurar alertas automáticas cuando un nodo se marque como “Unhealthy”.
- Issue comment#17JesusFSP2025-12-26 05:10Habilitar métricas en Azure Monitor (latencia, disponibilidad, tráfico).
- Issue comment#10JesusFSP2025-12-26 05:04Incluir evidencias de failover y distribución de tráfico.
- Issue comment#19JesusFSP2025-12-26 04:45Crear tablero de monitoreo con Azure Dashboard.
- Issue comment#18JesusFSP2025-12-26 04:42Configurar alertas automáticas cuando un nodo se marque como “Unhealthy”.
- Issue comment#13JesusFSP2025-12-26 04:39Configurar NSG para restringir tráfico entrante a solo HTTP/HTTPS.
- Issue comment#23JesusFSP2025-12-26 03:28Desactivar temporalmente una VM para probar failover automático.
- Issue#26JesusFSP2025-12-14 00:01Crear un Backend Pool con las VMs (VM-Web1, VM-Web2)
- Issue#25JesusFSP2025-12-13 23:59Implementar Azure Load Balancer (SKU Standard).
- Issue comment#24JesusFSP2025-12-13 23:58Crear un Public IP Address para el Load Balancer.
- Issue#24JesusFSP2025-12-13 23:57Crear un Public IP Address para el Load Balancer.
- Issue#30JesusFSP2025-12-13 23:56Documentar la arquitectura de red creada
- Issue#29JesusFSP2025-12-13 23:49Asignar IPs privadas fijas a las VMs.
- Issue comment#28JesusFSP2025-12-13 23:49Configurar Network Security Groups (NSG) con reglas para permitir puertos 80 y 443.
- Issue#4JesusFSP2025-12-13 23:40Validar conectividad interna entre las VMs.
- Issue#3JesusFSP2025-12-13 23:37Configurar roles de IIS o Apache en ambas VMs con una página de prueba.
- Issue#27JesusFSP2025-12-13 23:13Asociar la IP pública al Load Balancer.
- Issue#23JesusFSP2025-12-13 23:11Desactivar temporalmente una VM para probar failover automático.
- Issue#21JesusFSP2025-12-13 23:10Crear Load Balancing Rule para tráfico HTTP (puerto 80 → backend pool).
- Issue#20JesusFSP2025-12-13 23:09Configurar Health Probe en puerto 80 (HTTP).
Totals cover only the window loaded into ClickHouse and count events, not GitHub's lifetime totals — 0 stars here means stars gained during the window, not the repo's star count.