It was fun to present it in demos, but it can also be annoying to users.
I was pleasantly surprised to see him driving and trying to charge the car in public locations.
I am previously the founder of a synthetic monitoring startup, devraven.io.
Just sharing my experience - monitoring is brutally competitive. From my conversations most large enterprises have very little synthetic monitoring, they use DDOG or other APM tools and do not want to try any new tools for few thousand dollar savings. And in a lot of cases they are comfortable with their custom test frameworks that use Selenium. Some are even worried that setting up synthetic monitoring will bring down their environment or trash their database with junk data ::sigh::
Most smaller companies we spoke to are not mature enough to have monitoring and did not have resources who can setup monitoring. They used to ask us for help to build tests for them. Asks for discounts on $29.99/mo price point were not uncommon.
After few months of operating the product, we did find few angels who were interested in investing in us (not the product). But in the end, we did not feel that we can make good use of investor money and provide a decent return to them, so we ended up backing out of the investment and chose to shutdown the product.
Fair feedback. I definitely need to anchor myself to specific niche instead of saying it can work for anything and everything.
1. Create a Source for each customer and send customer specific data to each source. Configured pipelines for each source will receive the event data and processes it.
2. Create one source with multiple pipelines connected to it. In each pipeline, you can drop processing the data based on any conditions.
#1 is preferred so you are sure each customer's data is only reaching the pipelines configured for that customer data.
I’m basically doing web calls and parsing data, but the ServiceNow plugin is nice to have.
A ServiceNow integration is on my radar. But if you can provide more details I can definitely try to address it when I build the app. Please feel free to log an issue in github if you can provide any details or send an email to me (email in my profile).
https://google.github.io/A2A/#/documentation?id=multi-turn-c...
The sensitivity to prompts and response quality are related to an agent's functionality, A2A is only addressing the communication aspects between agents and not the content within.