Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Search - "l1 support"
-
L1 support requested to terminate an EC2 instance on which one of our apps seemed to be misbehaving. The node was terminated after few min.
L1 later realized that that instance didn't belong to that app, but instead it was one of the RabbitMQ nodes.
Then, after some panicking we remembered that HA was enabled, so nothing should've been lost.
Later, we realized that the recent RMQ upgrade necessitated a new cluster on which HA was NOT enabled!1 -
Spent 2 hours today doing L1 support work!!! God i hate working with lazy people!!!
2 hours wasted checking for an application bug on all deployed client pcs when the only issue is the printer has no fucking paper!!!
L1 and L2 support exists for these kind of issues!! Do your god damn jobs!!! -
(When L1 support fails to investigate before routing to L2)
User: I couldn’t able to view my files saved in network drive
Me: we have checked files on sever side its visible and u have access as well
User: my screen has broken so I couldn’t able to see
Rest is history1 -
Level 1 support moron dishing out bad instructions from his flowchart.
Wanted me to edit config files for a production setup, which would've killed shipping for all stations, in the middle of our shipping rush.
Fixed the problem while in the escalation queue for level 2. L2 confirms the fix, and bemoans the shit documentation L1 provided.
If its a business class (mission critical) system, hire decent support staff! You might try testing people for reading/listening comprehension, and then paying them a decent wage! This isn't good for my blood pressure...undefined l1 support shipping mouthbreathing flowchart monkey cheap business support bullshit outsourcing