Here is a good example of how real time @elastic logs/visualisations help with development (I've experienced this the first time many years ago when I doing a pentest that we had wired all server's logs into an ELK stack)
Prikaži ovu nit
-
I'm using two Elastic views for this First shows all events triggered by
@jira (and handled by the AWS Serverless workflow)pic.twitter.com/rkh2lTJ20G
Prikaži ovu nit
2nd view is a dashboard which is doing a search for particular issue value (this will allow use to see the contents of the data stored in @elastic to confirm that all that has been changed in Jira has been changed in Elastic)
Note the 'Task-11' filter on the top rightpic.twitter.com/lCQ7vWJfq2
-
-
To trigger the use case, first step is to create a new Issuepic.twitter.com/ak97MAOBHv
Prikaži ovu nit -
-
-
First view in
@elastic shows the two events we received from@Jirapic.twitter.com/wnQIPQ249R
Prikaži ovu nit -
and the dashboard shows the new issue too (it was picked up because the new issue has a link to 'Task-11')pic.twitter.com/uLMaUhu6PY
Prikaži ovu nit -
-
Task-11 has also been updated to include a link to Task-36pic.twitter.com/eKYJQwOgsS
Prikaži ovu nit -
-
-
-
and Task-11 being updated to NOT contain the link to the (now deleted) TASK-36pic.twitter.com/gCO48V6Q0F
Prikaži ovu nit
Kraj razgovora
Novi razgovor -
Čini se da učitavanje traje već neko vrijeme.
Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.