home.social

#incidentmanagement — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #incidentmanagement, aggregated by home.social.

  1. RE: infosec.exchange/@pwr2/1171944

    Thank you all, this was a really interesting poll! Not a single participant on Mastodon (expected) or LinkedIn (surprising!) wanted to hide the incident.

    Although in my experience, that is exactly what most companies do. Very common is the "outage unclear, investigation pending" answer.

    In my best cyber security case (communication-wise), the CEO actually approved that we share IOCs early. We received praise from the customers and not a single complaint. Not a single one.

    Be brave, incident managers! 💪❤️

    #infosec #cybersecurity #incidentresponse #IncidentManagement #dfir

  2. Production incident and the first question is: have we seen this before?

    I built a Quarkus service that turns Java incidents into vectors with deterministic feature hashing — no embedding model, no LLM. Store them in Qdrant, search by failure shape, filter by service and environment.

    The vectors are inspectable and repeatable. The scores are explainable from the input.

    New tutorial on The Main Thread:

    the-main-thread.com/p/incident

    #Quarkus #Java #Qdrant #VectorSearch #IncidentManagement

  3. Production incident and the first question is: have we seen this before?

    I built a Quarkus service that turns Java incidents into vectors with deterministic feature hashing — no embedding model, no LLM. Store them in Qdrant, search by failure shape, filter by service and environment.

    The vectors are inspectable and repeatable. The scores are explainable from the input.

    New tutorial on The Main Thread:

    the-main-thread.com/p/incident

    #Quarkus #Java #Qdrant #VectorSearch #IncidentManagement

  4. Production incident and the first question is: have we seen this before?

    I built a Quarkus service that turns Java incidents into vectors with deterministic feature hashing — no embedding model, no LLM. Store them in Qdrant, search by failure shape, filter by service and environment.

    The vectors are inspectable and repeatable. The scores are explainable from the input.

    New tutorial on The Main Thread:

    the-main-thread.com/p/incident

    #Quarkus #Java #Qdrant #VectorSearch #IncidentManagement

  5. Production incident and the first question is: have we seen this before?

    I built a Quarkus service that turns Java incidents into vectors with deterministic feature hashing — no embedding model, no LLM. Store them in Qdrant, search by failure shape, filter by service and environment.

    The vectors are inspectable and repeatable. The scores are explainable from the input.

    New tutorial on The Main Thread:

    the-main-thread.com/p/incident

    #Quarkus #Java #Qdrant #VectorSearch #IncidentManagement

  6. Production incident and the first question is: have we seen this before?

    I built a Quarkus service that turns Java incidents into vectors with deterministic feature hashing — no embedding model, no LLM. Store them in Qdrant, search by failure shape, filter by service and environment.

    The vectors are inspectable and repeatable. The scores are explainable from the input.

    New tutorial on The Main Thread:

    the-main-thread.com/p/incident

    #Quarkus #Java #Qdrant #VectorSearch #IncidentManagement

  7. New from me today: A roundup of Datadog #DASH2026 livestreamed engineering breakout sessions, which all touched on a common theme: that AI-driven #incidentmanagement tools only work if human #platformengineers have first designed a solid infrastructure and set of workflows.

    techtarget.com/searchitoperati #datadog #o11y #AI