{ Community }
  • Academy
  • Docs
  • Developers
  • Resources
    • Community Articles
    • Apigee on GitHub
    • Code Samples
    • Videos & eBooks
    • Accelerator Methodology
  • Support
  • Ask a Question
  • Spaces
    • Product Announcements
    • General
    • Edge/API Management
    • Developer Portal (Drupal-based)
    • Developer Portal (Integrated)
    • API Design
    • APIM on Istio
    • Extensions
    • Business of APIs
    • Academy/Certification
    • Adapter for Envoy
    • Analytics
    • Events
    • Hybrid
    • Integration (AWS, PCF, Etc.)
    • Microgateway
    • Monetization
    • Private Cloud Deployment
    • 日本語コミュニティ
    • Insights
    • IoT Apigee Link
    • BaaS/Usergrid
    • BaaS Transition/Migration
    • Apigee-127
    • New Customers
    • Topics
    • Questions
    • Articles
    • Ideas
    • Leaderboard
    • Badges
  • Log in
  • Sign up

Get answers, ideas, and support from the Apigee Community

  • Home /
  • Edge/API Management /
avatar image
0

Using scheduling for Apigee trace instead of manual work with control  

  • Export to PDF
Norbert Fodor created · Nov 22, 2020 at 09:54 PM · 164 Views

Currently we are using EdgeUI to start tracing for API testing and it's automatically turn off after 10 minutes so continuous monitoring needed during the tests. We want to automate this, and the goal is to use some scheduling or something like that, to start trace logging and stop after tests finished and save the logs to a specified place. Illustrated by an example: We know that one of our consumer wants to test our API named API-1 on 30th of November from 2 pm to 3 pm. We want to start trace without manpower at 2 pm and stop at 3 pm. After they finished their tests logs are should be saved to a specified folder.

Is it possible?

thub.nodes.view.add-new-comment
apigee edgeloggingtraceautomation
Add comment Show 4
10 |5000 characters needed characters left characters exceeded
▼
  • Viewable by all users
  • Viewable by Apigeeks only
  • Viewable by the original poster
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Viewable by all users
avatar image Priyadarshi Ajitav Jena · Nov 23, 2020 at 06:06 PM 0
Link

As per my understanding, trace is a live debugging tool. There is way to download trace using management api call.

avatar image Norbert Fodor · Nov 24, 2020 at 08:19 AM 0
Link

Maybe my question was not totally clear, so below you can see the trace tool, with a started trace session, which is limited to 10 minutes. We want to start trace sessions for APIs automatically (based on an agreement with our consumer) at a certain time for a given time range while the consumer doing tests and after the time frame expired trace session stopped and logs saved.

avatar image Norbert Fodor · Nov 24, 2020 at 08:22 AM 0
Link

As I see the picture is missing from my previous comment so I attached again.

apigeetrace.jpg (31.9 kB)
avatar image ylesyuk ♦ · Nov 27, 2020 at 08:27 PM 0
Link

Keep in mind that trace adds a processing overhead. So it should be used sparingly.

You can achieve not exactly this, but you can get pretty close by using this wrapper around management api so you can keep creating trace sessions using crontab or similar.

https://github.com/yuriylesyuk/ets

If you are on OPDK, you can use different approach to increase a number of requests, discussed here:

https://community.apigee.com/questions/39080/increasing-the-limit-of-trace-messages-in-edge-on.html

Here are examples of complicated situations when the tool was successfully used:

https://community.apigee.com/questions/71053/finding-one-error-among-thousands-of-successes.html

https://community.apigee.com/questions/79062/identify-source-of-30-second-proxy-latency.html

Article

Contributors

avatar image

Follow this article

137 People are following this .

avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image

Navigation

Using scheduling for Apigee trace instead of manual work with control

Related Articles

Apigee Edge - External Message Logging to ELK stack

cURL from Trace

Using Apache Freemarker in an Apigee Java Callout

OpenAPI2Apigee - 0.2.1 Version - Securing APIs using Swagger Spec & Apigee-127 Extensions

Apigee Edge - 4MV4D - Quota Policy - Message Weight - S02E05

How to trace a SOAP message on Apigee

Importing a credential (key+secret) into Apigee Edge, using Powershell

Apigee 4MV4D - Programming of APIs - Series - API Proxy Flows - S01E06

Apigee Edge - 4MV4D - Quota Policy - Calendar Type - S02E06

Apigee - 4MV4D - API Proxy - Trace Console

  • Products
    • Edge - APIs
    • Insights - Big Data
    • Plans
  • Developers
    • Overview
    • Documentation
  • Resources
    • Overview
    • Blog
    • Apigee Institute
    • Academy
    • Documentation
  • Company
    • Overview
    • Press
    • Customers
    • Partners
    • Team
    • Events
    • Careers
    • Contact Us
  • Support
    • Support Overview
    • Documentation
    • Status
    • Edge Support Portal
    • Privacy Policy
    • Terms & Conditions
© 2021 Apigee Corp. All rights reserved. - Apigee Community Terms of Use - Powered by AnswerHub
  • Anonymous
  • Sign in
  • Create
  • Ask a question
  • Create an article
  • Post an idea
  • Spaces
  • Product Announcements
  • General
  • Edge/API Management
  • Developer Portal (Drupal-based)
  • Developer Portal (Integrated)
  • API Design
  • APIM on Istio
  • Extensions
  • Business of APIs
  • Academy/Certification
  • Adapter for Envoy
  • Analytics
  • Events
  • Hybrid
  • Integration (AWS, PCF, Etc.)
  • Microgateway
  • Monetization
  • Private Cloud Deployment
  • 日本語コミュニティ
  • Insights
  • IoT Apigee Link
  • BaaS/Usergrid
  • BaaS Transition/Migration
  • Apigee-127
  • New Customers
  • Explore
  • Topics
  • Questions
  • Articles
  • Ideas
  • Badges